"We continue to take security seriously, now at scale." is gold aha.
Incident CVE-2026-LGTM
41–50 of 108 posts
Re: Incident CVE-2026-LGTM
#42That is very very funny, and oh so plausible. I enjoyed this bit a lot from the timeline > Karen Oyelaran finds the payload by reading the source code with her eyes and files a second issue. The triage assistant closes it as “duplicate of #8814.” Issue #8814 is a feature request for dark mode. Karen reopens it. The assistant closes it. Karen reopens it. Karen’s GitHub account is rate-limited for “patterns consistent…
Justice to Karen
> We would like to thank:
>
> Karen Oyelaran, who found the issue on Day 1 and is currently appealing her GitHub rate limit via a web form that is also AI-triaged
Re: Incident CVE-2026-LGTM
#43(I know its a satire, but could be seen as an actual post mortem of the future incident) This report made me realize there's no place for humans, as it is right now, in the process of building software systems in the future. Reading this incident made me dizzy after few paragraphs because of the cognitive context overload and I lost track multiple times.
I kinda felt it was satire, but then the below quote threw me off: > one vendor’s marketing team, cc’d on the cost anomaly alert, issues a press release citing “a 430% YoY increase in adversarial multi-agent security reasoning.” The stock opens up 6%. That happens! That is not satire. So i had to visit the comments here to be sure :)
Satire does usually have a degree of truth/realism.
Re: Incident CVE-2026-LGTM
#44Should have used Sigmashake guardrails... When will this industry learn. Youtube video: https://www.youtube.com/watch?v=SHZaMu6J0F0
Re: Incident CVE-2026-LGTM
#45I did not realize this was satire until like halfway through. That is how insane the times are becoming
Re: Incident CVE-2026-LGTM
#46If you're wondering what creats.io is - this is satire!
It's available for rental from the domain cartel if anyone wants to drop some $$ on making the joke just that little bit more real.
Re: Incident CVE-2026-LGTM
#47Perhaps a [Satire] note should be added to the headline.
Please don't! Getting tricked by the satire and then slowly realizing it's insane is half the fun.
Re: Incident CVE-2026-LGTM
#48Brought to you by the people who've been told repeatedly since mid 90s not to glue SQL strings together.
It's funny that as the most popular programming languages FINALLY got smart injection-safe SQL strings (js template literals etc), we're right back to square one with AI over the top that can't tell the difference between trusted and untrusted content. Funny and sad.
Re: Incident CVE-2026-LGTM
#49I did not realize this was satire until like halfway through. That is how insane the times are becoming
> That is how insane the times are becoming
Gee whiz what an interesting way of thinking.
Re: Incident CVE-2026-LGTM
#50> Approximately 11% of affected hosts were still running fish as their login shell following the February incident; this had no bearing on anything but is noted here for completeness Yeah, this one got me laughing and seems like such a heavy Claudism. The number of times I'm reading Claude's response and throwing my hands in the air like, "What the fck does that have to do with anything!?" It's the worst part of the…
One of the best CLAUDE.md improvements I've made is "don't talk like a Hacker News commenter". It seems to make a huge difference.
Yes, I recognize the irony.