October 26, 2026 · Edition #38 · by Asaf Nakash
Bug Bounties Are Pricing the Wrong Scarcity
I think bug bounties are pricing the wrong scarce resource.
The standard transaction still centers the report. HackerOne's own guidance says programs award bounties through submitted reports, often when a finding is confirmed as valid or after it is resolved. Its calculator starts with the affected asset and the report's severity. The money is attached to the finding, not to the full path toward a running fix.
AI is changing that cost curve. PHP says it closed 106 reports that were invalid, duplicate or unreproducible while publishing 15 CVEs since July 1. It also says AI tools have made reports much cheaper to write. Yet every verdict still requires a person to reproduce the issue, judge the impact and write or review the patch.
The two critical PHP flaws show what the bounty does not buy by itself. Maintainers had to design a compatible fix, test multiple supported branches, prepare source backports for older versions, coordinate mitigations with providers and help the ecosystem deploy. Discovery produced the input. Repair consumed the scarce capacity.
That does not make bug bounties obsolete. Human researchers still contribute novel attack paths, adversarial judgment and high-quality reproduction. But the reward should not stop economically at "valid."
A better model would split the incentive across the path to closure. Pay one part for a unique, reproducible finding. Reserve more for a maintainer-approved regression test and patch. Add rewards for necessary backports and verification that released packages, images or managed services actually carry the fix. Maintainers keep authority over compatibility and risk; AI can help reproduce, propose and test, but it should not push unsupervised changes into critical infrastructure.
This is not hypothetical. Google's Patch Rewards Program pays $100 to $15,000 for accepted security improvements to open-source projects. The patch must first be accepted by the maintainers and remain unreverted for a month. Google may also split the reward with maintainers when the change requires substantial work from the development team. Separately, five major technology companies have announced $12.5 million for tools and resources that help open-source maintainers filter, validate and remediate the growing volume of reports.
The bug bounty should become a sensor in a continuous remediation system: detect, reproduce, fix, test, release and verify. For critical open source, the companies that depend on the code should help fund that entire loop.
The next bounty should not end at the report. It should end at the running fix.
HackerOne bounty mechanics · Google Patch Rewards Program · PHP's report-handling account · Open-source remediation funding
Written by Asaf Nakash, Principal Product Manager for AI Security at Microsoft Defender and host of the Context Window podcast. Originally published in Context Window Edition #38, October 26, 2026.