On October 1, 2026, Google quietly paused one of its largest open-source bug-bounty programs, OSS VRP, for nearly a year — not over budget or compliance, but because AI-generated "plausible-looking" vulnerability reports drowned it. The official Google VRP account put it bluntly on X: "This pause is due to a significant rise in automated submissions, the vast majority of which are not valid." For a program launched in 2022 that paid researchers for flaws in Go, Angular, Protocol Buffers, and other core open-source Google projects, the move is effectively closing the inbound channel — at least temporarily.\n\n## The entry is paused, not the practice\n\nOSS VRP stopped accepting new product-vulnerability reports on October 1. Submission is not gone, but it has been redirected: most new reports are now steered into the Cloud VRP for select Google Cloud repositories, or into Google's Patch Rewards Program — both of which compensate fixes more than raw vulnerability submissions. Help Net Security reported that Google has effectively stripped payouts for the "product vulnerabilities" column of the OSS VRP reward table across all four project tiers (OT0 flagship down to OT3 low-priority). In short, Google will keep paying for fixes, but no longer for "report a product vulnerability that may not exist." Cloud VRP remains open, pre-October-1 reports continue, and Google has committed to a Q1 2027 redesign. The move isn't a withdrawal; it's an entry-gate rewrite.\n\n## Not an isolated event: AI widens both the inbox and the outbox\n\nOSS VRP is not the first casualty. Malwarebytes laid out the wider landscape: curl terminated its HackerOne bounty program in early 2026 because a tiny security team could no longer absorb the flood of mostly AI-generated, low-quality reports. Intel similarly ended cash payouts on its Intigriti bug-bounty program, reportedly for the same reason, per Phoronix. When code-capable models from OpenAI, Anthropic, and others cut the cost of producing a well-formatted CVE-style report to near-zero, the supply-side productivity ceiling got removed — but the receiver-side cost of building, reproducing, and deduping every submission did not.\n\nThat asymmetric drop — sender cost collapses, receiver cost unchanged — is classic spam economics. Concretely, writers can flood 100 submissions for the price of one, while reviewers still pay the full cost per submission. The result is invalid reports drowning out the valid ones. Google chose to shut the door for a year; curl chose to leave; Intel chose non-monetary recognition only.\n\n## The bar is set so low that AI-crafted vulns look real\n\nReports from early code LLMs were easy to triage — wrong API names, fabricated stack traces, garbled reproduction steps. That edge has eroded. Agent tools such as Cursor and Claude Code can clone a repository, run its build, read the traceback, and produce a structured vulnerability narrative that even seasoned reviewers need hours to disprove. Malwarebytes analyst Pieter Arntz framed this as an old weakness in disclosure economics that AI has now exposed: the cost of filing a plausible report has fallen sharply, while the cost of proving or disproving it remains human-intensive. His suggested fix is direct — let AI handle intake triage and only forward validated reports to engineers. Putting a robot at the gate sounds awkward, but it is operationally better than shutting the program for a year.\n\nIn practice, when OSS VRP reopens in Q1 2027 it almost certainly will not be the 2025 version again. The most likely redesign lands somewhere between: mandatory proof-of-concept evidence, raised minimum tier thresholds, deduplication tooling, and an internal AI filter layer ahead of human review. None of those are clean answers, but the alternative — letting the queue keep piling up — is worse.\n\n## The real cost lands on the open-source middle\n\nGoogle OSS VRP has dedicated headcount, Cloud VRP fallback, and a one-year runway to redesign. Most projects do not. Mid-sized open-source projects without dedicated security staff, which rely on HackerOne or community disclosure, now lose one of their natural escalation paths. They will either pay a commercial triage vendor, stand up their own AI review line, or quietly raise their disclosure threshold. In other words, Google's pause is also a stress-test of disclosure economics when the marginal cost of filing falls to near-zero. The total maintenance burden shifts onto smaller shoulders.\n\nThe lesson worth keeping is not which program Google paused. It is this: when LLM tooling drives submission costs toward zero while reviewer costs remain human-scale, the cost structure itself forces a redesign of public vulnerability disclosure — and Google's one-year pause is just the highest-visibility signal of that broader shift.