Post B6uxHXS1BnWDNxCC4e by gsuberland@chaos.social
 (DIR) More posts by gsuberland@chaos.social
 (DIR) Post #B6uxHX1mlKXE4avFBY by gsuberland@chaos.social
       1 likes, 0 repeats
       
       hmm. CVE-2026-41089 looks like a super basic stack buffer overflow in LSASS, straight out of a remote packet. I know Microsoft runs CodeQL over their code, and I can't envision a world where LSASS doesn't have coverage, so that raises questions about how it wasn't identified. my best guess is a process gap somewhere, but it would be cool to see a post incident report with info.(and before one of you mentions the slopcoding thought-terminating cliché, maybe think about it for a minute first)
       
 (DIR) Post #B6uxHXS1BnWDNxCC4e by gsuberland@chaos.social
       1 likes, 0 repeats
       
       even without a complete remote source flow to an unchecked buffer write sink I'd expect it to identify a potential stack buffer overflow like this, just with the default cpp rules. and I know MS has a whole suite of security and code quality rules on top of that. so it's pretty surprising.
       
 (DIR) Post #B6uxIpTBgHzLYkMG0G by Rairii@labyrinth.zone
       0 likes, 0 repeats
       
       @gsuberland my thoughts exactly