Broken official patches for Windows Shell Spoofing Vulnerability (CVE-2026-32202) 0patch.com/blog/micropatches…

We'd like to thank Maor Dahan (linkedin.com/in/maorisio/) with @akamai_research for sharing their analysis, which allowed us to create patches for Windows versions that are no longer receiving official updates from Microsoft - and for those with broken official patches.

It is pretty good at this when it doesn't default to everything being a safety violation. What's the next logical step? Likely AI driven 0patch and other proactive responses. Obfuscation systems designed to disrupt accurate assessments of attack surface. Evolution is the story.

Dropping a 0day? Consider having it 0patched first. 0patch.com/blog/dropping-a-0…

I'm not OP, but I do know a few things that can be done to make W7 safer and more usable. Security updates from Server 2008 R2 can be installed, those were still being released up until January 2026, so pretty recent still. Also, there are third party solutions such as 0patch, which will be issuing security patches until January 2028, but possibly longer if there is still demand. As for browsers, there's 2 options (at least for vanilla win7), Firefox 115 ESR, which is supported by Mozilla until August 2026 (they've been extending this constantly though) and there's Supermium, which is a fork of chromium and works on XP Also, for modern software compatibility, there is some exciting developments, mainly win32's secondsystem, which significantly improves compatibility with modern software. I know Adobe CC 2023 works with that, where the final versions to work ended at 2019/2020 depending on the software in question. Still early days yet, but we'll see how that goes.

Or no restarts at all - just hotpatching and 0patch style patches These monolithic patches that require reboots need to die

CVE-2026-21510 allowed malicious Windows shortcuts to execute remote DLLs without security warnings, bypassing mark-of-the-web protections. 0patch releases micropatches for legacy Windows systems after wild exploitation confirmed. #DFIR_Radar

We'd like to thank Oscar Zanotti Campo (linkedin.com/in/oscar-zanott…) for sharing their analysis and proof-of-concept, which allowed us to create a patch and protect 0patch users against this issue.

We'd like to thank Tianlin Zhang (@T0Zhang) for discovering this vulnerability and Clément Labro (infosec.exchange/@itm4n) for publishing their analysis, both of which allowed us to create a patch and protect 0patch users against this issue.

We'd like to thank SSD Secure Disclosure (@SecuriTeam_SSD) for discovering this vulnerability and publishing their analysis, which allowed us to create a patch and protect 0patch users against this issue.

Still on Windows 10, using 0Patch for updates. Working fine. 😎

42 years after my father and I had assembled it, our first computer "Galaksija" has found a new home at @muzej, where diligent caretakers of our regional computer history will have it displayed for nostalgic and curious visitors. Big thanks to @BSidesLjubljana for allowing me to show Galaksija to conference attendees before handing it over to the museum. Galaksija came as a DIY kit, requiring one to solder all components to the motherboard, assemble the keyboard, obtain additional chips from a small electronics shop in Austria, but most notably -- create one's own chassis. So each Galaksija is basically unique, ours having a wooden case for the computer, and a plastic box for the sound extension (attached at its back), both covered with black wallpaper. With its 6 KB of memory, even with a built-in BASIC interpreter, I was forced to learn coding in Z80 assembly to get anything interesting done. A minor detail in retrospect, but without that, @0patch would likely not exist today as we're writing our security patches in assembler. Thank you, dad, for bringing this machine to my life. It was a fun box with a huge impact for this 12-year-old then, as well as for thousands of @0patch users worldwide today.