GitHub slashes public bug bounty payouts by at least 50% across all severity levels starting July 27, 2026, while shifting top-tier rewards to a permanent invite-only VIP program. Critical vulnerability reports will now earn a fixed $10,000 in the public program, down from $20,000-$30,000+, with VIP researchers receiving $30,000 or more for the same caliber of findings.
The restructuring arrives as artificial intelligence transforms the vulnerability discovery landscape, making it cheaper to generate candidate findings while creating new challenges for triage teams. GitHub’s overhaul reflects a broader industry shift where first-pass discovery becomes commoditized, but verified, product-specific impact commands a growing premium.
Public Payouts Drop by Half as GitHub Overhauls Bug Bounty Program
Under the new structure taking effect July 27, 2026, GitHub’s public bug bounty program moves from flexible payout ranges to fixed payments at every severity level. The changes represent cuts of at least 50% for medium, high, and critical findings when measured against the previous ranges, with low-severity reports dropping approximately 59% from the bottom of GitHub’s prior rate table.
The new public payment schedule establishes:
- Low: $250, down from $617-$2,000
- Medium: $2,000, down from $4,000-$10,000
- High: $5,000, down from $10,000-$20,000
- Critical: $10,000, down from $20,000-$30,000+
Reports filed before the July 27 effective date, including those already in GitHub’s growing triage queue, will retain the previous payout terms. The company said fixed payments should remove uncertainty and triage overhead, though it may still award discretionary bonuses for exceptional work.
GitHub characterized the changes as a response to submission noise while promising established researchers faster responses, higher rewards, and closer access to its security engineering team. “You don’t earn more by submitting more. You earn more by submitting better,” the company stated.
VIP Tier Offers Premium Rewards for Invite-Only Researchers
The permanent invite-only VIP program replaces what was previously a quarterly eligibility review. The private tier’s payout schedule sets rewards substantially higher than the public program:
- Low-severity: $1,000
- Medium-severity: $7,500
- High-severity: $20,000
- Critical: $30,000 or more
Researchers can qualify for the private program by reporting at least one critical, two high, four medium, or seven low-severity vulnerabilities. The announcement does not specify a time window for meeting those thresholds or confirm whether qualification guarantees an invitation. GitHub said fuller criteria will appear on its public HackerOne program page.
The invite-only structure concentrates GitHub’s closest researcher relationships among people who have already succeeded inside the program. While this may improve speed and report quality, it also narrows the range of people examining the platform, potentially limiting one of the main advantages of a public bounty program.
As of July 22, GitHub’s rewards page still listed $20,000-$30,000+ for critical reports, while its FAQ retained the previous VIP eligibility test of at least $20,000 earned and two reports submitted during the preceding two years. The FAQ also said meeting those criteria did not guarantee an invitation and that GitHub reviewed candidates quarterly.
AI-Driven Vulnerability Discovery Reshapes Security Landscape
GitHub’s report controls arrive as artificial intelligence fundamentally changes the economics of vulnerability research. AI makes candidate findings cheaper to generate and code review cheaper to repeat. More researchers can produce potential findings, while internal teams can scan code, validate issues, and feed fixes into release and commit pipelines before an external report arrives.
One day before GitHub’s announcement, Google introduced Gemini 3.5 Flash Cyber, a lightweight model fine-tuned to find, validate, and patch software vulnerabilities. The model will initially be available exclusively to governments and trusted partners through CodeMender, Google’s code-security agent, as part of a limited pilot.
Google said the model can be invoked repeatedly to examine more code paths without using a larger frontier model for every attempt. The company positions it for frequent repository scans, time-sensitive launch reviews, and commit-scanning pipelines. In Google-run tests, Gemini 3.5 Flash Cyber found 55 unique confirmed V8 issues, compared with 47 for mainline Gemini 3.5 Flash and 36 for Claude Opus 4.6.
Google separately said its Cloud Vulnerability Research team used the model to find remote code execution flaws in public APIs and a memory-corruption flaw in a sensitive production service within two hours. The model then generated what Google described as a 100%-reliable RCE exploit that bypassed ASLR and W^X. The benchmark figures and production exploit result are Google-reported and have not been independently verified.
Signal Requirements and Entry Barriers for New Researchers
GitHub has not disclosed the HackerOne Signal threshold it will enforce, but says researchers below it will receive up to four initial submissions. Separately, HackerOne’s general rules give new researchers four trial reports per program within a rolling 30-day window.
Signal requirements and lower public rewards may suppress automated noise, but they can also make entry harder for capable researchers without an established HackerOne history. For a new researcher, a four-report program limit leaves little room for mistakes, unfamiliarity with GitHub’s security model, or a legitimate finding that is initially scored below expectations.
The restructuring follows a May 2026 policy change that demanded working proofs of concept, demonstrated impact, validation before submission, and closer attention to GitHub’s scope and ineligible findings.
What the Shift Means for the Vulnerability Research Ecosystem
A plausible-looking candidate finding is becoming abundant. Triage, exploit proof, product context, disclosure, and remediation remain constrained. A reliable exploit, a product-specific attack chain, or a finding that crosses a boundary the vendor misunderstood remains scarce.
Internal security teams can give an AI agent repository context, a project-specific threat model, and a validation environment tailored to the running system. Systems can then test findings, generate working proofs of concept, and propose fixes that account for system intent and surrounding behavior. The work can happen during development and on every relevant commit, rather than waiting for a scheduled assessment or an external report.
AI does not replace a penetration test, but source-code review, test generation, and first-pass validation are becoming easier to automate. Human testers retain more value where the work requires chaining weaknesses across trust boundaries, recognizing business-logic failures, modeling realistic attack paths, and proving material impact.
GitHub said it welcomes AI-assisted security research and already uses AI across its internal security programs. Researchers remain responsible for reproducing and verifying anything their tools produce. “The tools don’t matter. The quality of the work does,” the company stated.
GitHub’s new table prices the shift directly: $10,000 for a critical public finding and $30,000 or more for a critical VIP finding. First-pass discovery is getting cheaper. Verified, product-specific impact is where the premium remains.
What Bug Bounty Researchers Should Do Now
Security researchers participating in GitHub’s program should prioritize submitting any pending reports before the July 27 deadline to lock in current payout rates. New researchers should focus on understanding GitHub’s scope and ineligible findings thoroughly before making their initial submissions, as the four-report trial period leaves minimal margin for error.
Researchers capable of producing high-quality, verified findings with working proofs of concept should consider targeting qualification for the VIP tier, where rewards remain substantially higher. Those with established HackerOne histories may find the new structure rewards quality over quantity, but researchers without a track record face a more challenging entry path.
