Skip to main content
Mallory
← Back to News
standards-framework-updateai-enabled-threat-activity

cURL Ends Bug Bounty Program After Flood of Low-Quality AI-Generated Reports

Regulatory & Policy · 2 sources · Updated 5mo ago · First seen Jan 22, 2026

cURL Ends Bug Bounty Program After Flood of Low-Quality AI-Generated Reports

The cURL project ended its bug bounty program after maintainers reported being overwhelmed by a surge of low-quality, often AI-generated submissions that consumed significant triage time without yielding actionable security findings. cURL maintainer Daniel Stenberg documented the decision in a GitHub change (BUG-BOUNTY.md) indicating the bounty would stop at the end of January 2026, citing the “torrent” of submissions and the operational burden placed on the project’s security team.

Stenberg said recent bounty activity included multiple submissions that required substantial effort to assess yet did not describe actual vulnerabilities, and he expressed hope that removing financial incentives would reduce “crap and non-well researched reports,” whether AI-generated or not. While acknowledging that AI can sometimes assist in finding legitimate bugs, he encouraged researchers to continue reporting real security vulnerabilities even without payment, noting that the impact of ending the bounty on future reporting quality remains to be seen.

What this changes for youSee the reporting duties and controls this puts on the clock.
Get the context
Event timeline

How this story unfolded

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

2 events · Jan 21, 2026 – Jan 31, 2026
  1. Jan 31, 202610mo ago

    cURL bug bounty program scheduled to shut down

    The cURL project's bug bounty program was set to terminate at the end of January 2026 as part of an effort to reduce noise and remove incentives for poorly researched submissions. Stenberg said he still hoped researchers would continue reporting legitimate vulnerabilities without payment.

  2. Jan 21, 202610mo ago

    cURL maintainer announces end of bug bounty program

    Daniel Stenberg said the cURL project would end its bug bounty program at the end of January 2026 after an influx of low-quality, often AI-generated submissions created significant review overhead. He communicated the decision in a GitHub commit and a mailing list message, saying recent bounty reports did not describe actual security vulnerabilities.

Do you run this?See what this changes for your reporting obligations and which controls it puts on the clock.
Get the Regulatory Context
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.