chore: CVE-2026-45584

Signed-off-by: Xe Iaso <me@xeiaso.net>

Author: Xe

lume/src/shitposts/no-way-to-prevent-this/CVE-2026-45584.md

@@ -0,0 +1,20 @@
+---
+title: '"No way to prevent this" say users of only language where this regularly happens'
+date: 2026-05-20
+series: "no-way-to-prevent-this"
+type: blog
+hero:
+  ai: "Photo by Andrea Piacquadio, source: Pexels"
+  file: sad-business-man
+  prompt: A forlorn business man resting his head on a brown wall next to a window.
+---
+
+In the hours following the release of [CVE-2026-45584](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45584) for the project [Microsoft Windows](https://www.microsoft.com/en-ca/windows/), site reliability workers
+and systems administrators scrambled to desperately rebuild and patch all their systems to fix a memory safety vulnerability resulting in arbitrary code execution inside the virus scanner Windows Defender. This is due to the affected components being
+written in C++, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes
+these things just happen and there's nothing anyone can do to stop them," said programmer Dr. Annabelle Connelly, echoing statements
+expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have
+occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities. "It's a shame, but what can
+we do? There really isn't anything we can do to prevent memory safety vulnerabilities from happening if the programmer doesn't want to
+write their code in a robust manner." At press time, users of the only programming language in the world where these vulnerabilities
+regularly happen once or twice per quarter for the last eight years were referring to themselves and their situation as "helpless."