Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityai-platform-securitystandards-framework-update

AI-Driven Vulnerability Reporting Challenges for Open Source Projects

Vulnerability Disclosure · 45 sources · Updated 5mo ago · First seen Nov 12, 2025

AI-Driven Vulnerability Reporting Challenges for Open Source Projects

AI-powered tools from major technology companies such as Google and OpenAI are increasingly being used to discover vulnerabilities in open-source software, leading to a surge in bug reports for projects maintained largely by volunteers. While these AI systems, like Google's Project Naptime and OpenAI's Aardvark, have successfully identified significant flaws—including a critical vulnerability in OpenSSL (CVE-2024-9143) and a stack buffer underflow in SQLite—the volume and complexity of AI-generated reports are overwhelming open-source maintainers, many of whom lack the resources to address the influx, especially when reports lack accompanying patches.

The issue has prompted discussion within the open-source and security communities about the need for new frameworks and scoring systems tailored to AI-discovered vulnerabilities. At the 2025 OWASP Global AppSec USA conference, experts highlighted the limitations of traditional vulnerability scoring models like CVSS for AI-related threats and previewed the development of the OWASP AI Vulnerability Scoring System (AIVSS). This initiative aims to address the unique, non-deterministic risks posed by AI in software security, underscoring the growing recognition that AI-driven vulnerability discovery requires new approaches to risk management and remediation.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

21 events · Nov 10, 2025 – Jul 4, 2026
  1. Jul 4, 20265mo ago

    oss-sec moderator rejects purported SSRF disclosure as likely AI-generated

    In a July 4, 2026 oss-sec moderation reply, Solar Designer said a submitted 'Wasm OCI Image Fetcher Bearer Realm SSRF Bypass' report was almost certainly AI-generated, internally inconsistent, and unreliable. He also noted contradictions over whether the issue was private or public and said posting it to oss-security made it public.

    oss-sec: Re: Wasm OCI Image Fetcher Bearer Realm SSRF Bypass
  2. May 24, 20266mo ago

    Reporter alleges OpenStack exposed serious vulnerability report publicly

    In a May 24, 2026 oss-sec post, a reporter using the name ROI AI / Jacob said they had submitted about a dozen OpenStack issues and alleged that one serious security bug was made public by OpenStack, which they characterized as negligent. The post said the incident discouraged further reporting and highlighted disclosure-handling tensions around LLM-assisted vulnerability research.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  3. May 22, 20266mo ago

    Anthropic launches vulnerability disclosure dashboard with large OSS reporting totals

    Alan Coopersmith highlighted Anthropic's new coordinated vulnerability disclosure dashboard on oss-sec, alongside its Project Glasswing initiative. Anthropic said that as of 2026-05-22 it had privately disclosed 1,596 vulnerabilities across 281 open source projects, with 97 patched and 88 assigned CVEs or GitHub Security Advisories, while withholding project names and bug types until fixes are available.

    oss-sec: Anthropic's coordinated vulnerability disclosure dashboard
  4. May 22, 20266mo ago

    Jacob Bachmeyer says LLM-era embargoes may cost more than they protect

    In the ongoing oss-sec discussion, Jacob Bachmeyer argued that coordinated disclosure embargoes impose real operational costs on open-source projects and may provide limited security benefit if LLM-assisted tools let others, including attackers, rediscover the same vulnerabilities quickly. He suggested duplicate reports can indicate an issue is already quasi-public and should be fixed with greater urgency.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  5. May 22, 20266mo ago

    OpenStack issues cited as recent LLM-era coordinated disclosure cases

    In the oss-sec discussion, Tim Shephard said he had recently reported several OpenStack-related vulnerabilities, including Launchpad bugs #2149789, #2150261, #2149775, and #2150316, with three reportedly classified as critical and one as high. He also referenced a critical oslo rabbit man-in-the-middle issue that was difficult to fix without breaking deployments, providing a concrete example of LLM-era disclosure pressure on large legacy codebases.

    oss-sec: Sv: Coordinated Disclosure in the LLM Age
  6. May 21, 20266mo ago

    curl canceled bug bounty over AI-generated report flood

    During the ongoing oss-sec discussion, participants cited curl as having canceled its bug bounty program because maintainers were overwhelmed by excessive low-quality 'AI slop' vulnerability submissions. The example provided another concrete open-source ecosystem response to operational strain from AI-generated security reporting.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  7. May 21, 20266mo ago

    Jeffrey Walton backs defensive AI use but urges stronger test coverage

    In the ongoing oss-sec discussion, Jeffrey Walton cited Anthropic guidance recommending frontier models for defensive security tasks including bug triage, deduplication, reproduction, patch proposals, cloud misconfiguration analysis, pull request review, and secure migrations. He said such uses appear promising but warned that projects relying on AI for bug finding or triage need especially strong positive and negative test coverage because AI may operate without sufficient human oversight.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  8. May 15, 20266mo ago

    Yves-Alexis Perez warns sparse commit messages hinder downstream defenders

    In a May 15, 2026 oss-sec reply, Yves-Alexis Perez argued that stripping security-relevant detail from commit messages can backfire by hiding important fixes from downstream integrators and users. He said defenders cannot realistically inspect every commit in fast-moving projects, increasing the risk that security changes will be missed without explicit notice.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  9. May 11, 20266mo ago

    Tim Shephard warns public security analysis aids LLM-assisted variant discovery

    On the oss-sec mailing list, Tim Shephard argued that detailed public security reasoning in bug records, code reviews, commit messages, and advisories can help LLMs identify vulnerabilities, variants, regressions, and related insecure patterns. He proposed separating public fix and impact guidance from deeper technical analysis that could be shared through more restricted channels.

    oss-sec: Public security analysis and LLM-assisted variant discovery
  10. Apr 30, 20267mo ago

    Samba reports duplicate LLM-assisted bug discoveries during embargo periods

    In the oss-sec discussion, Douglas Bagnall said Samba was receiving duplicate reports of the same valid security issue from multiple independent groups using LLMs, with about one-third of valid security bugs being reported more than once while under embargo. The report provided concrete evidence that LLM-assisted discovery is eroding exclusivity in coordinated disclosure and increasing pressure for simultaneous patching.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  11. Apr 29, 20267mo ago

    EU CRA reporting obligations clarified to start on 2026-09-11

    In the oss-sec discussion, Santiago Ruano Rincón clarified that while the EU Cyber Resilience Act broadly applies from December 2027, Article 14 vulnerability and incident reporting obligations take effect earlier on 2026-09-11 under Article 71. The clarification refined Greg KH's point about future mandatory reporting of security fixes to EU authorities.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  12. Apr 29, 20267mo ago

    Greg KH cites EU CRA security-fix reporting as future visibility mechanism

    In the April 29, 2026 oss-sec discussion on disclosure in the LLM era, Greg Kroah-Hartman said upcoming European Union Cyber Resilience Act requirements would obligate projects to report security bug fixes to the EU by the end of the following year. He suggested this reporting could become a future source of visibility for downstream defenders even as maintainers reduce public security detail in commits and releases.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  13. Apr 29, 20267mo ago

    Willy Tarreau says LLM-era flaws should be treated as effectively public

    In an April 29, 2026 oss-sec reply, Willy Tarreau argued that vulnerabilities found with LLM assistance should be considered effectively already public because others can likely reproduce them with similar prompts. He said embargoes now increasingly delay fixes while users remain exposed, and noted he has adapted by reducing sensitive detail in commit messages and releasing fixes more quickly.

    oss-sec: Re: Coordinated Disclosure in the LLM Age
  14. Apr 28, 20267mo ago

    oss-sec warns public LLMs may undermine coordinated vulnerability disclosure

    Jeremy Stanley raised concerns on the oss-sec mailing list that public LLM services could weaken coordinated disclosure and embargo workflows by retaining or reusing prompts and outputs containing sensitive vulnerability details. He argued embargoed patch development and advisory drafting should avoid LLM assistance and suggested shorter embargoes may be necessary if LLM-assisted discoveries are effectively trivial to reproduce.

    oss-sec: Coordinated Disclosure in the LLM Age
  15. Apr 22, 20267mo ago

    Kernel developers propose removing ham radio networking stack over AI report burden

    Linux kernel developers discussed removing the AX.25, NET/ROM, and ROSE amateur radio protocols and related hamradio drivers from the mainline kernel, arguing the code is poorly maintained, attracts syzbot findings, and is now drawing AI-generated security reports. The discussion framed the issue as reducing attack surface from obscure, undermaintained subsystems, with some participants pointing to user-space alternatives and out-of-tree maintenance as substitutes.

    Kernel code removals driven by LLM-created security reports [LWN.net]
  16. Apr 22, 20267mo ago

    Linux kernel proposal targets legacy network drivers amid AI bug report burden

    A proposal submitted by Andrew Lunn to the Linux netdev mailing list called for removing numerous old ISA- and PCMCIA-era Ethernet drivers from the mainline kernel, arguing their unclear user base no longer justified the maintenance cost. The proposal cited growing strain from AI-assisted and fuzzer-generated bug reports and would remove roughly 27,646 lines of code if adopted, with drivers restorable if maintainers emerge.

    Linux may be ending support for older network drivers due to influx of false AI-generated bug reports - maintenance has become too burdensome for old largely-unused systems | Tom's Hardware
  17. Apr 15, 20267mo ago

    Cal.com moves production codebase private over AI-driven security concerns

    Cal.com announced that it is placing its core hosted production code and future development in a private repository, citing increased risk that AI systems can more easily find and exploit vulnerabilities in public code. The company said it will keep a stripped-down open-source version available as Cal.diy and had already moved critical security components such as authentication and data handling out of the public codebase.

    Cal.com goes private: A security reckoning for open source - The New Stack
  18. Apr 15, 20267mo ago

    Forescout warns AI will drive a surge in vulnerability discovery and exploit creation

    Forescout warned that advances in AI are likely to sharply increase both valid and false-positive vulnerability reports, potentially overwhelming CVE assignment and vendor triage processes. Its follow-up testing found all evaluated AI models could identify vulnerabilities and more than half could autonomously generate exploits, highlighting growing offensive as well as defensive implications.

    Brace yourselves for a vulnerability explosion, Forescout warns | IT Pro
  19. Mar 27, 20268mo ago

    HackerOne pauses Internet Bug Bounty submissions over AI-driven report overload

    HackerOne halted new vulnerability submissions to its Internet Bug Bounty program effective March 27, 2026, citing a mismatch between AI-accelerated vulnerability discovery and the limited capacity of open source maintainers to validate and remediate issues. The move marked a concrete industry response to mounting pressure from high volumes of low- to medium-quality AI-assisted reports.

    AI-Led Remediation Crisis Prompts HackerOne to Pause Bug Bounties
  20. Nov 12, 20251y ago

    ReversingLabs reports AI-generated vulnerability submissions overwhelming OSS maintainers

    ReversingLabs published analysis describing how AI-driven vulnerability reporting was flooding open-source software maintainers with low-quality or excessive submissions, creating operational strain in vulnerability handling. This marks a distinct development in the security ecosystem around AI-assisted disclosure practices.

  21. Nov 10, 20251y ago

    OWASP Global AppSec conference highlights AI risk management concerns

    An SC Media report from the OWASP Global AppSec event described industry discussion around AI security, criticizing superficial 'AI magic dust' approaches and the illusion of managed risk. The conference itself is the underlying real-world event reflected in the coverage.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

6 linked
OpenbsdFirefoxOpensslLinux KernelCurlClaude

Organizations

3 linked
AnthropicOpenaiGoogle
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.