Live data from Hacker News

New serious vulnerabilities spiked around release of Claude Mythos Preview

epoch.ai

71–80 of 82 posts

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#71

One of the major differences between Amodei’s and Hagseth’s views is that Hagseth said that in their world they don’t distinguish between “defensive” and “offensive” capabilities. In other words, a weapons missle defense system is equivalent to an attack one. I think that applying this thinking to software is a mistake. A lot of commercial software uses open source libraries under the hood, and and while the large co…

OpenAI gives access to cyber models for open source maintainers https://openai.com/index/patch-the-planet/

Both companies have cyber defense programs, but both 5.6 and Mythos are restricted by the government unfortunately.

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#72

One of the major differences between Amodei’s and Hagseth’s views is that Hagseth said that in their world they don’t distinguish between “defensive” and “offensive” capabilities. In other words, a weapons missle defense system is equivalent to an attack one. I think that applying this thinking to software is a mistake. A lot of commercial software uses open source libraries under the hood, and and while the large co…

How much money do you think a nation state has to spend on exploiting an OSS library? More or less than the owner of the OSS library? There's your answer.

Furthermore, of course Glasswing participants are scanning their dependencies as well. Why would you think they aren't!?

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#73

This is hardly news? We've known for months that a flood of AI-assisted vulnerabilities was coming; I posted on Twitter in March calling 2026 the year of a million CVEs: https://x.com/i/status/2035045573116789002

In pretty much every single HN post on this topic, there are a number of commenters claiming it’s false. Continued quantifiable data like this seems very important at hopefully resolving the ongoing disagreement about the facts.

Yes, there’s been a very popular narrative that Mythos’ abilities are just marketing fluff. I think it’s clear that there’s a real capability here, even if Anthropic’s communications have been heavily influenced by PR concerns.

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#74

This is hardly news? We've known for months that a flood of AI-assisted vulnerabilities was coming; I posted on Twitter in March calling 2026 the year of a million CVEs: https://x.com/i/status/2035045573116789002

In pretty much every single HN post on this topic, there are a number of commenters claiming it’s false. Continued quantifiable data like this seems very important at hopefully resolving the ongoing disagreement about the facts.

In pretty much every single HN post ~~on this topic~~, there are a number of commenters that are probably bots. Anyways it makes sense from a theoretical standpoint that LLMs should be able to find flaws in code better/faster than humans eventually, and its reasonable to think that time has come

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#75

Earlier quoted context omitted.

Its very hard to understand what you're saying with the comment - like you have 10+ years of experience and you verify each bug because you know Mythos can provide fake positives. But other teams (which also should have people equivalent to your skill and experience level) suck at it so much that CVP level workers are having to spend time on their fake reports. Then you say Anthropic should stop theater. Then you say…

I didn’t claim to have 10+ YoE; I said that most of the people in Project Glasswing are security researchers with 10+ YoE (avg). > Its very hard to understand what you're saying with the comment Yes, fair enough. I’m simply trying to shed some light on what goes on behind the scenes without disclosing too much information to avoid breaching the NDA(s) that all Project Glasswing users have signed. There’s a lot of spe…

Don’t worry, some of us remember Y2K and a) how much we fixed b) how much went wrong on the day and c) getting told it was a waste of time later.

And I didn’t even have to deal with a jumpy national government.

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#76
post #31

I do maintain dozens of C/C++/Perl projects. I got massive amounts of new good vulnerability reports, more than with the latest fuzzing waves. Fuzzing is still the majority overall, but Opus dominates now. Haven't got any Mythos/Fable vuln yet. And with the help of Sonnet/DeepSeek I can finally get around and weed out all the still existing fuzzing bugs. It has nothing to do with Mythos for me, just people getting An…

Are CVE really a good thing for open source projects?

No doubt is it a good thing to have issues reported and fixed, but CVE feels a bit like blackmailing maintainers - either you fix the issue or we get your project flagged with "security scanners".

I guess, my distaste mostly originates from randomly assigned high CVE numbers that don't reflect the actual threat. And the fact that it gives the companies which use the code "AS IS" an imaginary stick to hit open source maintainers, until they fix the issues for the company (for free of course).

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#77
post #58

One of the major differences between Amodei’s and Hagseth’s views is that Hagseth said that in their world they don’t distinguish between “defensive” and “offensive” capabilities. In other words, a weapons missle defense system is equivalent to an attack one. I think that applying this thinking to software is a mistake. A lot of commercial software uses open source libraries under the hood, and and while the large co…

If we take the noise about Mythos' capabilities as read, then releasing it freely into the world could result in chaos, as attackers find myriad new vulnerabilities and use them, and code owners frantically hunt for them and fix any that are exploited. (Noting, of course, how legendarily quick and agile large corporations aren't , compared to motivated individuals or small groups.). Eventually, given unfettered acces…

Given the choice of 1) just release it to all and hope for the best, and 2) phased-rollout roughly ordered by criticalness, I'm really not finding the advocates of 1 very persuasive.

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#78

One of the major differences between Amodei’s and Hagseth’s views is that Hagseth said that in their world they don’t distinguish between “defensive” and “offensive” capabilities. In other words, a weapons missle defense system is equivalent to an attack one. I think that applying this thinking to software is a mistake. A lot of commercial software uses open source libraries under the hood, and and while the large co…

Wouldn't open source enable review from people with access to the scanners prior to release? Seems like there is a fair chance that it will mostly be an actual spike, where's a bunch of existing vulnerabilities get cleaned up and then published software mostly has less vulnerabilities going forward.

Agreed. But this depends on (at least) 1 condition: that no new bugs are introduced.

FLOSS projects keep moving forward, and it seems some project's maintainers are being swamped by PRs (some good, some bad).

Whatever allows random 3rd party to 'strip-mine' existing codebases for bugs, should also be applied to new code.

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#79
post #31

I do maintain dozens of C/C++/Perl projects. I got massive amounts of new good vulnerability reports, more than with the latest fuzzing waves. Fuzzing is still the majority overall, but Opus dominates now. Haven't got any Mythos/Fable vuln yet. And with the help of Sonnet/DeepSeek I can finally get around and weed out all the still existing fuzzing bugs. It has nothing to do with Mythos for me, just people getting An…

Are CVE really a good thing for open source projects? No doubt is it a good thing to have issues reported and fixed, but CVE feels a bit like blackmailing maintainers - either you fix the issue or we get your project flagged with "security scanners". I guess, my distaste mostly originates from randomly assigned high CVE numbers that don't reflect the actual threat. And the fact that it gives the companies which use t…

It's good. It gives the maintainers the possibility to update their packages. And if a CVE is unfixed for months it reflects on the maintainance. This usually only happens to closed source packages.

Re: New serious vulnerabilities spiked around release of Claude Mythos Preview

#80

Earlier quoted context omitted.

The best case scenario for AI companies is, people receive those bug reports, look at the model that produced it and not even look at the details, just apply the fix mindlessly This gives Anthropic a staggering amount of power. Oh it came from Mythos? We will just lose time trying to analyze it, better apply the fix ASAP

Currently it looks like the opposite is happening haha, "oh it came from AI, let's discard it ASAP" is the trend in open source

And if it’s Mythos or Claude derived (a strong hint for Mythos), discard it faster.
Post reply on HN