this post was submitted on 19 Nov 2026
377 points (95.9% liked)

Technology

89924 readers
3351 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] JohnEdwa@sopuli.xyz 4 points 1 day ago (2 children)

Yes, a 55% false positive rate technically means more often than not, it isn't actually a valid vulnerability and it is wasting your time. But if you have 1000 boxes to go through while looking for a certain item, someone with a 50% false positive rate could identify two boxes for you, and it would be in one of them.

So unless that number is "AI claims there's a vulnerability on every other line of code you wrote", which I kinda doubt, and is actually based on made bug/vulnerability reports, then isn't is extremely helpful even if it's only right half the time?

[–] Aeder@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

The numbers are based on what happened to curl, since they are transparent about their results, and the ones that weren't false positives were underwhelming low severity vulnerabilities.

Of the 34 reports published so far, 19 have been marked as not a vulnerability, 6 have been confirmed as low severity, and 9 are still awaiting assessment. That puts the false positive rate at 55.9% so far, and only 17.6% of findings have been confirmed, all of them low severity. That's a lot of work dumped on open source maintainers for a small handful of low-impact bugs, and when a maintainer has to pace reports just to protect his team, that says plenty about the burden.

This also isn't new for curl. Back in May, Daniel wrote that five Mythos findings boiled down to a single confirmed vulnerability.

Here's the report: https://www.vulncheck.com/blog/anthropic-glasswing-november-update

[–] MrScottyTay@sh.itjust.works 6 points 1 day ago

Getting what I've seen even the actual vulnerabilities are the sort of stuff that is very very very hard to pull off, like it's identified a .2ms window where if you input something specific, you break something and gain access. Like race conditions that even though they theoretically exist, they're actually impossible to execute