Home / Blog / Google Project Zero Sets Course for 30-Day Disclosure…
Tech News

Google Project Zero Sets Course for 30-Day Disclosure Deadline

Google Project Zero eliminated its 30-day patch grace period and set phased deadlines to shrink bug disclosure windows to 30 days by January 2028.

By Dillip Chowdary • Nov 16, 2026 • Source: SecurityWeek

Google Project Zero Sets Course for 30-Day Disclosure Deadline
Image: SecurityWeek

At a glance

Program
Google Project Zero
Current deadline
90 days with no grace period
Intermediate deadline
60 days on February 2, 2027
Final deadline
30 days on January 3, 2028
Active exploit window
7 days
Disclosure exceptions
In-the-wild exploits and rare hardware flaws

Google Project Zero eliminated its 30-day patch grace period and scheduled an aggressive reduction of its public vulnerability disclosure timeline down to 30 days, citing the growing pressure of automated vulnerability discovery and exploitation. Natalie Silvanovich, a security engineer at Google Project Zero, announced the immediate implementation of the Full X disclosure model along with future milestones in SecurityWeek's report. Under this framework, security research findings will become public strictly on deadline whether or not a vendor has finished rolling out a patch.

This report details the concrete milestone dates, policy mechanics, exception boundaries, and technical quality standards governing Project Zero bug reports through 2028. It provides enterprise security teams, software maintainers, product security incident response groups, and vulnerability researchers with the operational expectations required to adapt internal patching pipelines. Software creators must align their development workflows with faster remediation cycles as external disclosure timelines shrink across the industry.

01End of the thirty-day grace period

Under the historical policy, Project Zero gave software vendors 90 days to develop a patch and offered an additional 30-day grace period to roll that fix out to end users. Starting November 13, the security team removed that 30-day rollout grace period entirely from its disclosure terms. The change forces organizations to complete development, testing, and deployment within the primary disclosure window.

The revised baseline operates under what Project Zero calls the Full X policy. Under these rules, Project Zero publishes technical vulnerability details exactly 90 days after reporting them to the vendor. The publication occurs regardless of whether a vendor has released a functional fix or when that update arrives for customers.

02Phased disclosure timeline to thirty days

The initiative introduces scheduled contractions over the next several years rather than cutting disclosure windows overnight. On February 2, 2027, Project Zero will shorten its standard public disclosure window from 90 days to 60 days. The deadline contracts again on January 3, 2028, when the team establishes a permanent 30-day window between initial vendor notification and public advisory release.

This phased transition prevents immediate operational disruption while establishing firm target dates for vendor security teams. Project Zero structured the multi-year progression to give organizations time to modernize their patch development and validation pipelines. Software maintainers must gradually accelerate their response workflows before the tighter deadlines take effect across all standard reports.

Policy phaseDisclosure deadlineGrace periodActive exploitation window
Prior policy90 days30 days7 days
Full X policy90 daysNone7 days
February 2027 phase60 daysNone7 days
January 2028 phase30 daysNone7 days

03Active exploit exceptions and rare waivers

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Beyond shortening core timelines, Project Zero is removing most special cases from its standard operating rules. Bugs that are already known to be actively exploited in the wild will retain Google's standard seven-day public disclosure deadline. Vulnerabilities that have already been made public by outside researchers or third parties also remain exempt from the standard timeline.

If a vendor finishes its remediation work early, Project Zero permits early publication upon request. Natalie Silvanovich confirmed that the team will publish advisory details ahead of schedule when maintainers ask for immediate public release. This flexibility allows coordinated announcements once fixes have been safely deployed to users.

Note: Serious vulnerabilities may still receive deadline extensions on rare occasions under Project Zero oversight. The research group preserved historical precedent from hardware security crises like Spectre and Meltdown, ensuring exceptional systemic flaws receive custom handling when industry-wide coordination is strictly necessary.

04Remediation infrastructure and attacker discovery speed

The structured timeline reduction directly addresses the growing risk that users remain exposed to unpatched security flaws for prolonged periods. Silvanovich explained that an immediate shift could cause vendors to rush fixes for newer reports while neglecting older, more critical vulnerabilities. The multi-year ramp gives engineering departments time to systematically upgrade their patching tools and response infrastructure.

Project Zero selected a schedule designed to encourage vendors to improve their remediation speed without establishing unattainable operational demands. Silvanovich noted that the group hopes the policy leads vendors to improve processes so they can remediate all reported vulnerabilities quickly. A defect's severity influences its eventual impact on end users, but severity does not lower the probability that automated attackers will discover the flaw independently.

AI-assisted vulnerability discovery and automated exploitation techniques have drastically shortened the window before attackers weaponize flaws. Defensive engineering pipelines must evolve to match the speed at which external actors find and leverage systemic software weaknesses. Project Zero expects that tightening disclosure intervals will force organizations to eliminate manual bottlenecks in their deployment systems.

05High report standards for reproducibility and impact

Project Zero applies these stringent disclosure timelines only to bugs that demonstrate substantial severity and verified impact. The research group holds its own submissions to strict technical standards regarding reproducibility, readability, reachability, and demonstrated security consequences. Silvanovich affirmed that the team's disclosure policy assumes all incoming findings satisfy this rigorous quality bar.

The policy acknowledges that maintainers face different operational realities when evaluating external bug reports of varying quality. Silvanovich stated that software vendors can reasonably handle lower-quality submissions differently than verified reports delivered by elite research teams. Maintainers can direct their urgent remediation capacity toward well-documented, reproducible flaws that present clear attack paths.

By pairing shorter timelines with comprehensive vulnerability data, Project Zero aims to make rapid remediation feasible for recipient organizations. The detailed reports provide engineers with the proof-of-concept material needed to diagnose root causes without prolonged triage delay. Vendors can focus immediately on engineering solutions rather than clarifying whether reported conditions represent genuine security threats.

Frequently asked questions

When does Google Project Zero eliminate the 30-day grace period?

Project Zero eliminated the 30-day patch deployment grace period starting November 13 under its Full X policy. Reports are now published 90 days after notification regardless of vendor patch status.

What is the timeline for Project Zero's 30-day disclosure deadline?

Project Zero will reduce its disclosure window to 60 days on February 2, 2027. The final 30-day disclosure deadline takes effect on January 3, 2028.

How does the policy handle zero-day bugs exploited in the wild?

Actively exploited vulnerabilities retain Google's standard seven-day disclosure deadline. Flaws already disclosed publicly by third parties are also exempt from standard timelines.

Can vendors request early disclosure of fixed vulnerabilities?

Yes, Project Zero permits early publication of vulnerability details ahead of the deadline if the vendor requests it. The team also retains exceptions for rare hardware vulnerabilities such as Spectre and Meltdown.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →