GitHub Cuts Public Bug Bounty Payouts by Half, Moves Top Rewards Behind a New Invite-Only VIP Tier
GitHub is halving public bug bounty payouts starting July 27, reserving its largest rewards for a new invite-only VIP tier as it fights a flood of low-quality, AI-generated reports.
Editor's Note ·
- Correction:
- The article states the new VIP tier payouts ($1,000/$7,500/$20,000/$30,000+ for low/medium/high/critical) match 'the top of the old public range' across the board. That is only true for high ($20,000 = old top of $10,000-$20,000) and critical ($30,000+ = old top of $20,000-$30,000+). For low severity, the old public range topped out at $2,000, not the $1,000 VIP payout; for medium, the old public range topped out at $10,000, not the $7,500 VIP payout. The VIP tier does not match the old ceiling at every severity level.
Overview
GitHub is restructuring its bug bounty program to cut public payouts by at least half at every severity level, redirecting its largest rewards to a new invite-only tier for proven researchers, according to a GitHub Blog post. The new pay scale takes effect for any report filed on or after July 27, 2026, as reported by The Hacker News.
What We Know
Under the new public program table published by GitHub, payouts are set at $250 for low-severity findings, $2,000 for medium, $5,000 for high, and $10,000 for critical vulnerabilities. According to The Hacker News, those figures represent cuts of at least half across the board: low-severity payouts previously ranged from $617 to $2,000, medium from $4,000 to $10,000, high from $10,000 to $20,000, and critical from $20,000 to $30,000 or more.
The steepest rewards now sit behind a new permanent, invite-only VIP tier, which GitHub says pays $1,000 for low-severity findings, $7,500 for medium, $20,000 for high, and $30,000 or more for critical bugs, matching the top of the old public range, according to GitHub. The Hacker News reports that researchers can qualify for that private program by reporting at least one critical, two high, four medium, or seven low-severity vulnerabilities.
GitHub is framing the change as an incentive redesign rather than a simple cost cut. “The core shift here is in what we’re incentivizing: you don’t earn more by submitting more. You earn more by submitting better,” the company wrote in its blog post. GitHub said the restructuring is meant “to reduce the volume of low-effort and AI-generated reports,” and it is pairing the new pay scale with a HackerOne signal requirement on the public program. Researchers who haven’t yet built a track record on HackerOne’s platform get “up to four initial submissions” before that threshold applies, per the same post.
Existing submissions are shielded from the cut. “Reports submitted before these changes take effect will be honored under the previous bounty structure,” GitHub wrote, adding that it is “grandfathering the backlog so that only reports made on or after July 27, 2026 will be assessed with the new structure,” according to GitHub’s blog post.
The July payout overhaul follows an earlier round of changes GitHub announced in May 2026, when it began requiring a working proof of concept for every submission. “Show us the impact, don’t just describe it. What could an attacker actually achieve? We need a working proof of concept that demonstrates real exploitation and concrete security impact,” GitHub wrote at the time in a separate blog post. That May update also introduced a shared-responsibility framing for reports that hinge on a user trusting untrusted content, with GitHub senior security researcher Jarom Brown telling CSO Online that in such cases “the security boundary is the user’s decision to trust that content.” Brown also said the company is not opposed to AI-assisted research itself: “We have no problem with researchers using AI tools. AI is a force multiplier,” he told CSO Online, while adding that not every valid report reflects real risk, since “not every valid submission represents a meaningful security risk.”
What We Don’t Know
GitHub’s announcement does not specify a time window for researchers to hit the VIP qualification thresholds, nor does it say whether meeting them guarantees an invitation into the private tier, The Hacker News notes. It is also not yet clear how many active public-program researchers will be affected by the new HackerOne signal requirement once the four-submission grace period is used up.
Analysis
The restructuring lands at the intersection of two pressures GitHub has been navigating for months: a surge in AI-generated vulnerability submissions that has strained its security team’s triage capacity, and a desire to keep its most experienced researchers engaged rather than losing them to competing programs. By collapsing the public program’s top payouts while preserving — and in some cases matching — the old top-tier rates inside a harder-to-reach VIP program, GitHub is effectively betting that fewer, higher-quality reports from a smaller pool of vetted researchers will do more for its security posture than a larger volume of public submissions of uneven quality.