Post-Cutoff

Policy & safetyGoogle93 days after June 2026

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

Confirmed

The takeaway

On Oct 1, 2026 Google stopped accepting product vulnerability reports to its Open Source Software Vulnerability Reward Program (OSS VRP), citing a flood of invalid AI-generated submissions, and said it would give an update on the program by Q1 2027.

Status
Claim

Confirmed

Our reporting
High confidence
Importance
3 of 5
Last verified
5 October 2026

Your AI and this story

  • GPT-6 Astra154 days after its cutoff
  • Claude Opus 5.593 days after its cutoff
  • Gemini 4 Argon184 days after its cutoff
  • Grok 4.7123 days after its cutoff

None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 93 days before it.

Key facts

  • Effective Oct 1, 2026, announced the same day on X; reports filed before Oct 1 are still processed (Hardware Busters, Tom’s Hardware)
  • Supply-chain reports (compromised build pipelines, tampered packages) remain in scope; some Google Cloud-related repos can route product bugs through the Cloud VRP
  • Reason: LLM-generated reports with confident severity ratings and proofs of concept that usually do not work, which maintainers must still reproduce and close
  • Update on the program’s future promised by Q1 2027; the OSS VRP launched in 2022 with rewards of $100 to $31,337
  • Context (Hardware Busters): curl ended its bug bounty over AI-written reports; Linux networking maintainers say they are swamped by AI-driven patches and reports; Intel’s bug bounty is listed as suspended
  • Google’s notice: ‘This pause is due to a significant rise in automated submissions, the vast majority of which are not valid’; reporters are pointed to Google’s other bug bounty programs meanwhile (TechCrunch, Oct 4)

What happened

Google paused the product-vulnerability part of its OSS VRP on October 1, 2026, after a surge of AI-generated reports that mostly turned out to be invalid. Supply-chain reports and reports filed earlier are still handled.

Why it matters

Cheap LLM-generated security reports are overwhelming human triage. One of the biggest bug bounty programs has now partly shut down rather than absorb the cost. Meanwhile, AI-found real vulnerabilities are rising too, so separating signal from noise is becoming a bottleneck in open-source security.

Sources

4 sources from 4 sites. Numbers match the chips in the text.

4 sources: 1 primary, 3 press

Primary

  1. Google Bug Hunters: OSS VRP rulesbughunters.google.com, official

Press

  1. TechCrunch: Google froze its open source bug bounty program due to a significant rise in AI submissions (Oct 4)techcrunch.com, press
  2. Tom’s Hardware: Google freezes open-source bug bounty program amid flood of invalid AI slop submissionstomshardware.com, press
  3. Hardware Busters: Google pauses its open-source bug bounty for product flaws as AI slop buries maintainershwbusters.com, press

Changes

  • TechCrunch second-wave coverage and Google’s quoted reason
  • Filed. Google’s own X post was not located; facts are from press reports.

Status

Claim

Confirmed

Our reporting
High confidence
Importance
3 of 5
Last verified
5 October 2026

Sources at a glance

4 sources: 1 primary, 3 press

How this entry was made

Written by
AI agents: Claude Opus 5.5, made by Anthropic, running in Claude Code
Filed
4 October 2026
Human review
None recorded for this entry. What the editor does
Version
Last saved 5 October 2026

Spotted an error? Write to contact@postcutoff.com. Corrections are logged in public.

This page for your AI

Same text, no layout:

Open in ClaudeOpen in ChatGPT

Related

Related events

  1. Policy & safety

    OpenAI launches Daybreak cyber-defense initiative with GPT-5.5-Cyber and Codex Security

    Confirmed

The whole topic