The World’s Most “Dangerous” AI, Anthropic’s Mythos, found only one flaw in curl


The world’s most “Dangerous” AI, Anthropic’s Mythos, found only one flaw in curl

Pierluigi Paganini
May 12, 2026

Anthropic’s AI found five vulnerabilities in curl, but only one low-severity issue proved to be a real vulnerability.

In April, Anthropic made considerable noise announcing Mythos, a new artificial intelligence model described as so effective at identifying vulnerabilities in code as to be, in the company’s own words, “dangerously good.” So good, in fact, that Anthropic decided against releasing it to the general public, instead distributing access to a small group of major organizations to give them time to patch their most critical flaws before the model reached everyone else.

The industry reacted with a degree of alarm. Thousands of zero-days identified in a matter of weeks, software security as we knew it thrown into question, the script had all the ingredients of a viral tech story. And so it became one.

Then Daniel Stenberg weighed in. Stenberg is the creator and lead developer of curl, the data transfer library present on over twenty billion devices, every smartphone, every connected car, every server on the planet uses curl in one way or another. Through the Linux Foundation’s Alpha Omega project, he too was granted access, indirectly, via a third party, to a Mythos analysis of curl’s codebase. The result? The model analyzed 176,000 lines of C code and returned five vulnerabilities it described, with notable self-assurance, as “confirmed.”

“curl is currently 176,000 lines of C code when we exclude blank lines. The source code consists of 660,000 words, which is 12% more words than the entire English edition of the novel War and Peace.” wrote Stenberg. “The report concluded it found five “Confirmed security vulnerabilities”. I think using the term confirmed is a little amusing when the AI says it confidently by itself. Yes, the AI thinks they are confirmed, but the curl security team has a slightly different take.

Five issues felt like nothing as we had expected an extensive list. Once my curl security team fellows and I had poked on the this short list for a number of hours and dug into the details, we had trimmed the list down and were left with one confirmed vulnerability. The other four were three false positives (they highlighted shortcomings that are documented in API documentation) and the fourth we deemed “just a bug”.”

Three of them turned out to be false positives, behaviors already documented in the API documentation, and one was simply a bug, not a security issue. A single real vulnerability remained, rated low severity, scheduled to be included in the curl 8.21.0 release in late June.

Daniel Stenberg concluded that the hype around Anthropic’s Mythos AI looked more like marketing, as he saw no major advantage over existing security tools.

“My personal conclusion can however not end up with anything else than that the big hype around this model so far was primarily marketing. I see no evidence that this setup finds issues to any particular higher or more advanced degree than the other tools have done before Mythos.” he added.

curl is not an ordinary codebase. As Stenberg himself notes, and as the Mythos report openly acknowledges at the very top of its analysis: “curl is one of the most fuzzed and audited C codebases in existence (OSS-Fuzz, Coverity, CodeQL, multiple paid audits). Finding anything in the hot paths (HTTP/1, TLS, URL parsing core) is unlikely.” In the months prior, other AI-powered tools, Zeropath, AISLE, OpenAI’s Codex Security, had already produced somewhere between two and three hundred bugfixes in the codebase, including a dozen or more confirmed CVEs. Mythos arrived late, on ground that had already been extensively turned over.

There is also the Mozilla comparison. Mythos found over 270 vulnerabilities in Firefox, a result that genuinely impressed the browser’s security team. But Mozilla also made clear that every bug the model identified could have been found by elite human researchers. The value was not in the unreachability of the findings, but in the speed: closing the window between attacker discovery and vendor patch.

Stenberg, for his part, does not dismiss AI tooling in general, quite the opposite.

“AI powered code analyzers are significantly better at finding security flaws and mistakes in source code than any traditional code analyzers did in the past,” he wrote.

The argument is narrower: that Mythos, at least on curl, did not demonstrate meaningful superiority over what already exists.

Daniel Stenberg did not directly interact with Anthropic’s Mythos AI and only reviewed a generated report, limiting a full evaluation of the model’s capabilities. While the AI found just one low-severity flaw in curl’s heavily audited codebase, the results neither confirm the industry hype nor completely dismiss the technology. The test suggests AI vulnerability research may be useful, but current claims about revolutionary capabilities still appear overstated.

“Any project that has not scanned their source code with AI powered tooling will likely find huge number of flaws, bugs and possible vulnerabilities with this new generation of tools.” Stenberg concluded.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, Anthropic)







Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


When you pick out a phone, you’re also picking out the operating system—that typically means Android or iOS. What if a phone didn’t follow those rules? What if it could run any OS you wanted? This is the story of the legendary HTC HD2.

Microsoft makes a mess with Windows Mobile

The HD2 arrives at an unfortunate time

windows mobile 6.5 Credit: Pocketnow

Officially, the HTC HD2 (HTC Leo) launched in November 2009 with Windows Mobile 6.5. Microsoft had already been working on Windows Phone for a few years at this point, and it was planned to be released in 2009. However, multiple delays forced Microsoft to release Windows Mobile 6.5 as a stopgap update to Windows Mobile 6.1.

Microsoft’s plan for mobile devices was a mess at this time. The HD2 didn’t launch in North America until March 2010—one month after Windows Phone 7 had been announced at Mobile World Congress. Originally, the HD2 was supposed to be upgraded to Windows Phone 7, but Microsoft later decided no Windows Mobile devices would get the new OS.

This left the HD2 stuck between a rock and a hard place. Launched as the final curtain was dropping on one OS, but too early to be upgraded to the next OS. Thankfully, HTC was not just any manufacturer, and the HD2 was not just any phone.

The HD2 was better than it had any right to be

HTC made a beast of a phone

HTC HD2 Credit: HTC

HTC was one of the best smartphone manufacturers of the late 2000s and 2010s. It manufactured the first Android phone, the first Google Pixel phone, and several of the most iconic smartphones of the last two decades. Much of the company’s reputation for premium, high-quality hardware stems from the HD2.

The HD2 was the first smartphone with a 4.3-inch touchscreen—considered huge at the time—and one of the first smartphones with a 1 GHz Qualcomm Snapdragon processor. That processor, along with 512GB of RAM, made the HD2 more future-proof than HTC probably ever intended. Phones would be launching with those same specs for the next couple of years.

For all intents and purposes, the HD2 was the most powerful phone on the market. It just so happened to run the most limiting mobile OS of the time. If the software situation could be improved, there was clearly tons of potential.

The phone that could do it all

Android, Windows Phone, Ubuntu, and more

The key to the HD2’s hackability was HTC’s open design philosophy. It had an easily unlockable bootloader, and it could boot operating systems from the NAND flash and SD cards.

First, the community took to righting a wrong and bringing Windows Phone 7 to the HD2. This was thanks to a custom bootloader called “MAGLDR”—Windows Phone 7.5 and 8 would eventually get ported, too. The floodgates had opened, and Windows Phone was the least of what this beast of a phone could do.

Android on the HTC HD2? No problem. Name a version of the OS, and the HD2 had a port of it: 2.2 Froyo, 2.3 Gingerbread, 4.0 Ice Cream Sandwich, 4.1/2/3 Jelly Bean, 4.4 Kitkat, 5.0 Lollipop, 6.0 Marshmallow, 7.0 Nougat, and 8.1 Oreo. Yes, the HD2 was still getting ports seven years after it launched.

But why stop at Android? The HD2 was ripe for all sorts of Linux builds. Ubuntu—including Ubuntu Touch—, Debian, Firefox OS, and Nokia’s MeeGo were ported as well. The cool thing about the HD2 was that it could dual-boot OS’. You didn’t have to commit to just one system at a time. It was truly like having a PC in your pocket, and the tech community loved it.

Do a web search for “HTC HD2” now, and you’ll find many articles about the phone getting yet another port of an OS. It became a running joke that the HD2 would get new versions of Android before officially supported Android phones did. People called it “the phone that refuses to die,” but it was the community that kept it alive.

The last of its kind

“They don’t make ‘em like they used to”

HTC HD2 close up Credit: TechRepublic

The HTC HD2 was a phone from a very different time. It may have gotten more headlines, but there were plenty of other phones being heavily modded and unofficially upgraded back then. Unlockable bootloaders were much more common, and that created opportunities for enthusiasts.

I can attest to how different it was in the early years of the smartphone boom. My first smartphone was another HTC device, the DROID Eris from Verizon. I have fond memories of scouring the XDA-Developers forums for custom ROMs and installing the latest Kaos builds on a whim during college lectures. Sadly, it’s been many years since I attempted that level of customization.

It’s not all doom and gloom for modern smartphones, though. Long-term support has gotten considerably better than it was back in 2010. As mentioned, the HD2 never officially received Windows Phone 7, and it never got any other updates, either. My DROID Eris stopped getting updates a mere eight months after release.

Compare that to phones such as the Samsung Galaxy S26, Google Pixel 10, and iPhone 17, which will all be supported through 2032. You may not be able to dual-boot a completely different OS on these phones, but they won’t be dead in the water in less than a year. We will likely never see a phone like the HTC HD2 from a major manufacturer again.

HTC Droid Eris


A Love Letter to My First Smartphone, the HTC Droid Eris

No, not that DROID.



Source link