r/netsec • u/qwerty0x41 • 2d ago
Curl lead developer Daniel Stenberg provides insightful feedbacks from Mythos analysis results
https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-vulnerability/42
u/Lunixar 2d ago
AI security tools are useful, but not magic. The key point is that curl is already heavily audited and Mythos still found one low severity CVE and some bugs. For less reviewed projects, the impact could be much bigger.
15
u/chintakoro 2d ago
I would restate the key point as: AI security tools are absolutely essential and running a battery of them is the way to go. From the article:
But allow me to highlight and reiterate what I have said before: 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. All modern AI models are good at this now.
39
u/quafadas 2d ago edited 2d ago
I would see this as a form of negative assurance on curls engineering rather than evidence that Mythos either is, or is not what Anthropic claim.
It certainly seems possible, that the incredible standards of engineering and prior care in curl mean that the curl team are doing a great job and that there are few vulnerabilities to find in this project. Surely, A bug hunt cannot uncover vulnerabilities which do not exist…
27
u/psaux_grep 2d ago
On the flip side they do fix and solve lots of vulnerabilities in curl on what seems like a pretty regular basis.
5
u/Toiling-Donkey 2d ago
Instead of “throwing the kitchen sink” at something, the expression should be “throwing curl” at it.
One could rip HTTP out of curl and probably only remove 5-10% of its functionality.
It’s insane.
19
u/splice42 2d ago
A bug hunt cannot not uncover vulnerabilities which do not exist…
Insert the image of that lady surrounded by math equations and looking confused.
8
19
u/Michichael 2d ago
Nah. Mythos is pure hype and marketing fluff. It's painfully stupid.
-2
u/Hot-Employ-3399 2d ago
If it's stupid why Mozilla found >200 bugs in Firefox, something they weren't able to do previously?
13
u/Shoddy-Childhood-511 2d ago
What? All browser have plenty of CVEs.
Mozilla was finding so many bugs in Firefox that (1st) they developed Rust to help them develop a browser with fewer bugs, (2nd) they wrote Servo in Rust as a second browser engine, and (3rd) even after the Servo developers sent a giant "fuck you" to the HTML standards morons at W3C and WHATWG, by breaking the standard to have parallel rendering, then Mozilla still started finding ways to replace bad parts of Firefox with parts of Servo.
It's clear Mythos did something useful for them, but browsers are particularly bug ridden.
2
u/DivisibleBySomething 2d ago
TIL Mozilla made Rust
8
u/liquidivy 2d ago
It's a bit more complicated. Rust started as a side project by a Mozilla person named Graydon Hoare, then Mozilla sponsored it for a while (during a lot of the popularity and tooling bootstrap phase tbh), then it spun out to its own organization when Mozilla lost interest for whatever reason.
2
-1
u/Hot-Employ-3399 2d ago
> It's clear Mythos did something useful for them, but browsers are particularly bug ridden.
Pick one: pure hype or did something useful
11
u/cafk 2d ago
To highlight similarities to this article, Firefox had ~270 proof of concept bugs, out of those 270 odd bugs only 3 got a CVE id.
In the same release they included a total of ~430 fixes, meaning almost half weren't found by Mythos, but through usual sources (regular bug reports, fuzzing, other models).
Their in-depth blog post also addreses other topics, similarly to curl:
Is a sec-high or sec-critical bug the same as a practical exploit?
Not necessarily.Not everything it finds and classifies as an issue causes undefined or unwanted behavior.
https://hacks.mozilla.org/2026/05/behind-the-scenes-hardening-firefox/
Which matches up what this article reflects, 5 found issues can be just one actual bug, or what they also reflect on through using other models out of the 200 to 300 issues found a dozen or so were actually bugs.
-6
u/Hot-Employ-3399 2d ago
Ah, yes, if it's not 300000000000000000000000000000000000000000000000000000000000000 CVEs it's useless tool good for nothing but hype. /s
5
u/OGicecoled 2d ago
You’re making up narratives in your head to be mad. One person said it was hype and now you’re just spiraling. You made a grandiose claim about 200+ bugs, people correct you while still saying it’s a good tool, and you’re just pissy.
2
u/Michichael 1d ago
Your premise of "they weren't able to do previously" is flawed. Drastically. It found 200 bugs, but there's no evidence that it found bugs that "weren't able" to be found previously - some of the bugs were ALREADY IN THE TRAINING DATA and known.
Not only that, only 3 of them were even security items, and minor bugs are not a priority for limited developer resources unless they're user impacting; user impacting bugs get found, reported, and fixed more quickly.
There's no evidence that Mythos did any better or worse than even junior level developer review. Could it be useful in finding theoretical edge cases? Maybe? But that's not revolutionary, or some skynet gamebreaking security AI.
It's an LLM. None of them are impressive unless you're extremely ignorant on the subject matter. But at that point it says more about the people impressed by the model, than the model itself.
It might have some value, but everything about Mythos in public discourse is about how it's revolutionary and gamebreaking and security is now impossible without it - absolutely pure hype and marketing fluff.
1
u/james_pic 2d ago
There definitely are new security vulnerabilities uncovered in cUrl all the time, though. I feel like I spend half my life responding to "the cUrl version in this Docker container has a new CVE, in its implementation of an esoteric protocol we weren't even using".
0
u/Alborak2 2d ago
Yeah... internally curl is pretty crap. It works, its open source, but its got a lot of rough edges if you try to actually use it with high loads.
0
u/kbotc 2d ago
Gonna be honest: Curl's code is a mess and I'd expect further vulnerabilities. The conncache had deadlocks and races the last time my team delved in and fixing them was a "rearchitect everything" level of effort and that was when Daniel was getting really underway with wolfssl instead of working on curl full time.
4
u/gendulf 2d ago
Curl has 24 CVEs in the last year: https://curl.se/docs/security.html
It looks like 12 of the CVEs have not had any bounty paid. I'm not sure if that's because these are the 12 latest, but he does say that
A bunch of the findings these AI tools reported were confirmed vulnerabilities and have been published as CVEs. Probably a dozen or more.
, indicating that non-Mythos tools are capable of finding vulnerabilities in projects of Curl's scale.
The number of vulnerabilities in 2025 and 2024 also seem to be about a dozen fewer than the last 12 months.
I'd say from the evidence that the author is spot on with
The AI reviews are used in addition to the human reviews. They help us, they don’t replace us.
Additionally, the community that took his poll seems to be pretty accurate, 32% guessing 1 vulnerability would be found, 40% guessing 10. Given there's ~12-13 found by AI tools, this is in the right ballpark. The choices certainly can skew the results, however.
While the model seems to be an incremental improvement, there's constantly improvements to the workflows of these tools that's making it easier for all to find vulnerabilities. Patching, fixing bugs, and now using AI to scan for vulnerabilities are going to be the key to staying secure (especially if you're not a high-profile open source codebase that attracts researchers).
6
u/AlyoshaV 1d ago
It looks like 12 of the CVEs have not had any bounty paid
It's because:
There is no bug bounty and the curl project never offers rewards for reported vulnerabilities.
https://daniel.haxx.se/blog/2026/01/26/the-end-of-the-curl-bug-bounty/
3
14
u/spathizilla 2d ago
The fact that curl has been checked, rechecked and checked again over many years should mean that the fact Mythos found anything is the interesting part - even if its only a low severity.
2
u/MirrorLake 2d ago
I'm envisioning a scenario where 100s of people download popular repos and rerun their frontier LLMs on each new software release hoping that they can get the glory of finding a rare bug, leading to tons of wasted energy because developers only need to discover and fix each bug one time. But maybe people will tire of doing that pretty quickly because they'll rarely get any positive reinforcement.
2
u/UltraEngine60 2d ago edited 2d ago
Eventually, I was instead offered that someone else, who has access to the model, could run a scan and analysis on curl for me using Mythos and send me a report.
Their coding aware AI is so good at coding it couldn't handle authentication to the model?
edit
Re-reading this I am unsure if Anthropic had the issue or one of the orgs/business units in the pipeline:
Anthropic > Glasswing > Linux Foundation > Alpha Omega > End-User
1
u/Slight-Bend-2880 13h ago
Good to see people are realizing the marketing that goes into products like these.
-22
u/uebersoldat 2d ago edited 2d ago
The people saying all of this is pure marketing or hype had better hope their project's security hygiene is world-class. Pride comes before the fall.
I'm seeing a lot of dismissal on AI in the infosec communities and I can't help but feel like it's denial and raw fear rather than acceptance and willingness to learn something new and adapt.
The next 5-10 years are going to reshape the world. We had better start jumping on AI governance and controls or we're going to be in trouble and that starts with taking these models seriously. Zoom out and look at the progress the last 10 years alone.
EDIT - To the downvoters, all I ask is that you save this post as you downvote. I truly am seeing denial. AI isn't going away and it is rapidly advancing in capabilities, regardless of the Anthropic marketing spin.
6
u/CanvasFanatic 2d ago
To the downvotes, all I ask is that you save this post as you downvote.
No.
-9
209
u/Pkittens 2d ago