News for hackers. Stuff that matters.
Re:Project Glasswing: An Initial Update by skybrian on Friday May 22, 2026 @06:19PM (#48242367)
As the article explains, they mostly haven't been disclosed, because they're not fixed. They're giving people 90 days, or 45 after a patch is made.
Re:Project Glasswing: An Initial Update by gck1 on Friday May 22, 2026 @07:10PM (#48242737)
> haven't been disclosed, because they're not fixed.

That's convinient.

But wait, don't they have this amazing AI that can fix all the issues itself with a single /goal command? What's the holdup?

Re:Project Glasswing: An Initial Update by solenoid0937 on Friday May 22, 2026 @07:21PM (#48242828)
You should really read the article, every question asked so far in this thread has been very clearly answered.

I miss the days when HN would RTFA.

Re:Project Glasswing: An Initial Update by Amekedl on Friday May 22, 2026 @11:01PM (#48244174)
Just keep spewing your fanboy bile, eventually you'll realize the ignorance.
Re:Project Glasswing: An Initial Update by dyauspitr on Saturday May 23, 2026 @03:46AM (#48245634)
He doesn’t want to read the article. He just wants to LLM bad.
Re:Project Glasswing: An Initial Update by TOMDM on Friday May 22, 2026 @10:46PM (#48244080)
From the article

> As we noted above, the bottleneck in fixing bugs like these is the human capacity to triage, report, and design and deploy patches for them.

...

> To begin, we’ve released Claude Security in public beta for Claude Enterprise customers. It’s a tool that helps teams scan their codebases for vulnerabilities, and which can generate proposed fixes for them. In the three weeks since launch, Claude Opus 4.7 has been used to patch over 2,100 vulnerabilities. (This is faster than the open-source patching described above in large part because enterprises are fixing their own code, whereas open-source fixes usually require volunteer maintainers who work through coordinated disclosure.)

Your critique of the article would likely land much better if you engaged with it.