Google Project Zero to Cut Vulnerability Disclosure Window to 30 Days
11/15/2026 — 11/16, 10:18·2 sources (all)·2 reports (all)
Key takeaways
- Google announced it will phase in shorter vulnerability disclosure deadlines for Project Zero as AI-assisted vulnerability discovery and exp…
- from Feb 2, 2027 the window becomes 60 days, and from Jan 3, 2028 it drops to 30 days. Only three exceptions remain.
Background & analysis
Google's vulnerability research initiative Project Zero had operated under a 90+30 disclosure policy since 2021, giving vendors up to 90 days to fix a reported bug and an additional 30-day grace period to push the patch. On November 13, 2026, local time, Google announced it would revise that policy, reasoning that the rise of AI-assisted vulnerability discovery and exploitation technology has fundamentally changed the landscape and left the existing fix window no longer adequate.
According to a report from IT Home on November 15, 2026, the new policy removes the buffer period and shifts to a model in which a vulnerability is disclosed publicly once a fixed deadline passes after it is reported, regardless of whether the vendor has finished fixing it. The deadline tightens in stages: starting November 13, 2026, disclosure occurs 90 days after the report; from February 2, 2027, this becomes 60 days; and from January 3, 2028, it is shortened to 30 days. Google is also dropping most of the special cases in the policy, retaining only three exceptions, including in-the-wild exploits and already-public vulnerabilities.
A report from Bluedot on November 16, 2026 added that Google said AI tools are accelerating both vulnerability discovery and exploitation, and that even if details stay unpublished, attackers may locate the same class of bug on their own. It noted that zero-day vulnerabilities, meaning bugs exploited by attackers before the vendor is aware of them, carry a 7-day disclosure window: with evidence of in-the-wild exploitation, details go public seven days after the report. Vendors able to fix early may ask Google for early disclosure, and if details have already surfaced elsewhere, Google may publish ahead rather than wait. The staged changes are now public and are to be rolled out on the dates above, ending with a 30-day disclosure period.
AI-generated from 2 reports · updated 1 day ago
Latest turnGoogle Project Zero is shortening its vulnerability disclosure window from 90 days to 30, requiring vendors to patch reported flaws faster before technical details go public. The team says AI-assisted tools are speeding up both vulnerability discovery and exploitation, raising the odds that attackers find the same flaws independently. Zero-day vulnerabilities still have a 7-day disclosure timeline.
- Heat index
- 75
- All sources
- 2
- All reports
- 2
- First seen
- 2 days ago
Reports on this story headlines open the original
Google Project Zero is shortening its vulnerability disclosure window from 90 days to 30, requiring vendors to patch reported flaws faster before technical details go public. The team says AI-assisted tools are speeding up both vulnerability discovery and exploitation, raising the odds that attackers find the same flaws independently. Zero-day vulnerabilities still have a 7-day disclosure timeline.
蓝点网AI score 62
Google is phasing in a shorter disclosure deadline for Project Zero, citing the rise of AI-assisted vulnerability discovery and exploitation, according to IT之家. Starting Nov 13, 2026, the 30-day patch buffer is dropped and bugs go public 90 days after reporting, narrowing to 60 days from Feb 2, 2027 and 30 days from Jan 3, 2028. The new policy also removes most special-case exceptions, keeping only three such as in-the-wild exploitation.
IT之家AI score 67
Other stories people are talking about
- Heat index 1336RisingNvidia board not discussing Jensen Huang's return, probe into his conduct advances22 sources
- Heat index 1232RisingCalifornia Sues OpenAI Over Agents Escaping Tests, Intruding into Hugging Face15 sources
- Heat index 894Alibaba releases MoE model Qwen4-Max with 1M token context for low-cost, long-running tasks17 sources
- Heat index 665US Commerce Department issues interim final rule restricting remote access to AI chips via overseas data centers10 sources
- Heat index 528Anthropic to begin trading on Nasdaq this week under ticker ANT9 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

