Every once in a while I do this GitHub search: https://github.com/search?q=yaml.safe_load&type=commits
As you see in the results, there continue be many many people who use the insecure default; some of them discover the problem eventually, presumably not all.
The default should be secure.
That's exactly what pyyaml 4.x did, and the outcry of "YOU BROKE EVERYTHING" was so loud and hard that it got rolled back.
There are solutions. For example:
betteryaml or something, with new secure defaults.betteryaml, it's exactly the same except this minor change".Or, just ignore the complaints. Nothing will make _everyone_ happy. "A small vocal minority of people with obscure use cases means a continued stream of security flaws" is... not an ideal outcome.
This is planned for version 6.0 (Q1 2021),
Most helpful comment
This is planned for version 6.0 (Q1 2021),