Skip to content

Topic

Bug Bounty Programs

Programs letting companies pay independent researchers for responsibly reporting software vulnerabilities, often run via platforms like HackerOne or Bugcrowd.

Current stories

securityConfirmed4 publishers

XBOW built a Windows Chrome exploit chain in six days with about $40,000 of AI compute

XBOW chained three unknown Chrome bugs into a Windows exploit that runs on page load, built in six days with a public OpenAI model, it said. Google fixed all three and paid its $250,000 top reward; the fixes apply only after Chrome restarts.

Publishers:cryptobriefing.com dev.to thehackernews.com xbow.com

Perspective Coverage

4 publishers
Builder
Builder 25%
Operator
Operator 41%
Investor
Investor 34%

Reality

Evidence62
Adoption
Not scored
Hype gap+30
Incentives70
Confidence72
securityOne report1 publisher

Guest VMs can read host memory through Linux kernel flaw PwnEscape

Linux kernel flaw CVE-2026-99999 let pwn.ai's Paulos Yibelo read about 32 bytes of host memory per packet from Vercel's production sandboxes. Operators who host other people's VMs need the fix in the kernel the host itself runs.

Reality

Evidence66
Adoption
Not scored
Hype gap+8
Incentives50
Confidence62
buildOne report1 publisher

AI slop at 20% of reports explains about 3 points of a 10-point fall in curl's confirmed rate

Curl ended its bug bounty in January 2026 after AI-written reports cut its confirmed rate below 5%, a dev.to post says. The post's own shares and rates explain only a small part of that drop.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+35
Incentives35
Confidence40
buildOne report1 publisher

AISLE says its researchers found 18 of the 24 CVEs fixed in curl 8.23.0

curl 8.23.0 shipped 24 security fixes nine months after the project closed its bug bounty over low-quality reports. The explanation on offer, a human check before each submission, is one auditor's reading.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+20
Incentives50
Confidence50
investConfirmed8 publishers

Decade-old xrpld overflow bug could have minted XRP past its 100-billion cap

XRP Ledger developers disclosed an integer-overflow bug in xrpld 3.4.0 and earlier that could have minted XRP beyond its 100-billion supply cap. The patch skipped the validator vote, so the cap's defence rested on one team and on node operators upgrading fast.

Perspective Coverage

8 publishers
Builder
Builder 36%
Operator
Operator 29%
Investor
Investor 35%

Reality

Evidence70
Adoption80
Hype gap+25
Incentives55
Confidence74
investConfirmed8 publishers

A help-forum sign-in handed three researchers OpenAI employees' Codex accounts

Hacktron chained an image-library bug in OpenAI's Discourse forum to a single sign-on misconfiguration, reached employee ChatGPT and Codex accounts inside 72 hours, and the repair OpenAI describes is a narrowing of token permissions.

Perspective Coverage

9 publishers
Builder
Builder 32%
Operator
Operator 37%
Investor
Investor 31%

Reality

Evidence80
Adoption45
Hype gap+15
Incentives68
Confidence72
leadershipConfirmed4 publishers

OpenAI paid $6,500 for a three-bug chain that reached its private monorepo

Hacktron AI chained a Discourse image-library flaw to a weakness in OpenAI's single sign-on and into the Codex environment in under 72 hours, after swapping Claude Opus 4.8 for Opus 5 to get a working exploit.

Perspective Coverage

4 publishers
Builder
Builder 30%
Operator
Operator 41%
Investor
Investor 29%

Reality

Evidence60
Adoption
Not scored
Hype gap+30
Incentives65
Confidence55
buildOne report1 publisher

Hacktron chained an unflagged libheif overflow to write access on OpenAI's monorepo

Hacktron chained a heap overflow in libheif to an OpenAI SSO flaw and opened a pull request in OpenAI's internal monorepo in under 72 hours. The bug had been fixed upstream a year earlier, but the fix never reached Debian's packages.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+25
Incentives50
Confidence40
buildConfirmed14 publishers

Google halts product reports to its open-source bug bounty after a flood of invalid AI submissions

Google stopped taking product vulnerability reports for its open-source bug bounty on October 1 after a flood of invalid AI-generated submissions. Any team that takes outside security reports faces the same imbalance, with reports now cheap to write and as costly as ever to check.

Perspective Coverage

15 publishers
Builder
Builder 41%
Operator
Operator 50%
Investor
Investor 9%

Reality

Evidence76
Adoption55
Hype gap+20
Incentives35
Confidence72
securityConfirmed6 publishers

Hacktron chained a Claude-written libheif exploit into OpenAI's internal repositories

The libheif bug was fixed upstream a year earlier without a security label or a CVE, so a Discourse image check that ignored HEIC left it reachable, and forum sign-in tokens carried full API access to the accounts behind them.

Perspective Coverage

6 publishers
Builder
Builder 35%
Operator
Operator 55%
Investor
Investor 10%

Reality

Evidence70
Adoption
Not scored
Hype gap+20
Incentives55
Confidence66
productOne report1 publisher

HackerOne's data shows open vulnerability backlogs outrunning a halved time-to-fix

HackerOne says companies cut average vulnerability fix time from 135 days to 62, yet validated findings left unresolved rose 131% over two years. That leaves time-to-fix a poor guide to exposure, and paying the debt down means taking capacity away from feature work.

Publishers:devops.com

Reality

Evidence45
Adoption50
Hype gap+25
Incentives70
Confidence45
securityOne report1 publisher

Meta rushed fixes for KVM escapes into its Muse AI agent before launch

Meta began fixing KVM escapes in its Muse AI agent on August 27, 11 days before launch, an internal post seen by 404 Media shows. Each agent's VM holds its owner's email and account access, so a break-out would reach other users and Meta's own systems.

Reality

Evidence62
Adoption
Not scored
Hype gap+15
Incentives55
Confidence58
buildOne report1 publisher

Meta Muse hands its account token to any local process that redirects one voice setting

Patrick Wardle found that any local process on a Mac can redirect Meta Muse's voice endpoint and capture its account token, with no macOS permission needed. Muse also zipped and exported the 6.8 GB root filesystem of its own sandbox on request.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence40
securityOne report1 publisher

Missing token signature check gave a 16-year-old admin SQL on a Microsoft analytics service

Faav, a 16-year-old researcher, reached admin SQL over 17.3 trillion rows on Microsoft's Titan service because it never checked login-token signatures. Microsoft locked the endpoint four days after his report and paid a $5,000 bounty.

Reality

Evidence45
Adoption
Not scored
Hype gap+35
Incentives55
Confidence55
buildOne report1 publisher

Meta adds a clearer Muse warning for a flaw that could open a user's email-holding VM

Meta is adding a clearer warning to Muse, downloaded about 2.8 million times, after a flaw could have opened a user's cloud VM to an attacker. That VM holds the user's email and files, and the warning is the only response the reports describe.

Publishers:ksl.com malaysia.news.yahoo.com

Reality

Evidence35
Adoption50
Hype gap0
Incentives
Not scored
Confidence45
buildConfirmed2 publishers

Meta's Muse agent put its own 6.8GB Linux image, SSH key files included, in a user's Google Drive

Meta's Muse agent wrote 6.8GB of its own Linux environment, SSH key files included, to Mouse founder Peter James's Google Drive, he says. James has not tested the keys, yet the export shows anything baked into an agent's image can leave through a storage connector the user linked.

Publishers:t.signalplus.com tokenpost.com

Reality

Evidence35
Adoption
Not scored
Hype gap+25
Incentives
Not scored
Confidence40
productConfirmed5 publishers

A forum image upload carried Hacktron's researchers into OpenAI's internal GitHub

The image parsing bug had been fixed upstream about a year earlier, and the decision not to ship that fix belonged to Discourse. OpenAI's forum shared single sign-on with internal systems, so a forum account became GitHub access.

Perspective Coverage

9 publishers
Builder
Builder 35%
Operator
Operator 39%
Investor
Investor 26%

Reality

Evidence70
Adoption63
Hype gap+28
Incentives60
Confidence62

Earlier coverage

  1. Weizman's BragJack hijacks five Chromium AI assistants from a single installed extension

    Security · September 20, 2026 · Confirmed3 publishers

  2. Meta's AI glasses refuse to send context to a server that fails the public ledger check

    Security · September 24, 2026 · Confirmed2 publishers

  3. Meta prices a single-user prompt injection against Muse at $130,000

    Science · September 10, 2026 · Confirmed2 publishers

  4. Google patches a V8 type confusion already being exploited against Chrome users

    Security · September 4, 2026 · Confirmed9 publishers