Technology news and discussion on TalkFuse.
GitHub slashes public bug bounty payouts as AI report flood buries its security team
GitHub is overhauling its public bug bounty programme from 27 July 2026, cutting payouts for openly submitted reports while creating a new invite-only tier with much higher rewards for researchers with a proven track record. The Microsoft-owned company says the change is a response to a surge of low-quality and AI-generated submissions that have overwhelmed its security team, and it hopes redirecting funds towards vetted researchers will improve the quality of reports it receives.
Under the revised public programme, low-severity findings drop from $500–$1,000 to $250, medium-severity rewards fall from a $5,000 cap to $2,000, high-severity payouts are cut from up to $20,000 to $5,000, and critical vulnerabilities now max out at $10,000 rather than $30,000. The new VIP tier, by contrast, pays up to $1,000, $7,500, $20,000 and at least $30,000 respectively across the same severity bands, with entry based on a history of accepted reports. GitHub is also adopting HackerOne's "signal requirement" to cap how many reports newcomers can submit before proving themselves, though it will allow up to four attempts and will honour the old payout rates for reports already in its backlog.
In short
- GitHub cuts public bug bounty rewards from 27 July 2026
- New invite-only tier offers much higher payouts for proven researchers
- Move aims to curb flood of low-quality, AI-generated reports
Steelman: both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
GitHub faces a genuine operational crisis where AI-generated and low-quality submissions are drowning out legitimate security research, preventing the team from investigating actual vulnerabilities. By concentrating resources on vetted researchers through the VIP tier, the company can maintain programme viability whilst focusing on reports likely to be genuinely useful. With finite security resources, it makes pragmatic sense to pay substantially more for high-confidence research rather than wade through a majority of submissions that waste investigative time.
The case against
The changes substantially restrict opportunity for emerging security researchers and newcomers by cutting public payouts by up to 67% and imposing submission limits, creating a gatekeeping effect that could exclude talented researchers without established track records. Rather than address the root cause through better submission filters or intake vetting, GitHub shifts costs onto the broader research community. Open bug bounty programmes serve as public goods benefiting security overall; restricting them prioritises short-term operational convenience over accessibility to security research.
Explained simply
GitHub, the code-sharing platform owned by Microsoft, runs a programme that pays security researchers to find and report bugs in its systems. From July 2026, it is restructuring this programme by cutting the money paid to researchers who submit reports through its public system, whilst creating a separate scheme with significantly higher rewards for researchers with a proven track record.
The company says it has been overwhelmed by a flood of poor-quality submissions, many of them generated by artificial intelligence tools, which has stretched its security team beyond capacity. By redirecting its budget towards researchers it has already verified as reliable, GitHub hopes to focus on reports that are genuinely useful rather than spending time sorting through unsuitable submissions.
The change reflects a wider challenge facing companies that rely on bug bounties to find security flaws: as more people and tools submit reports, separating the genuinely helpful from the noise becomes increasingly difficult. For security researchers, the restructuring means new entrants will earn less money per report, though those with proven success records can now earn more.
AI Cybersecurity Research Science Technology