Google Project Zero Sets 30-Day Vulnerability Disclosure Window
┌─ google-project-zero-30-day-disclosure.md :: hero
Google Project Zero is shortening its vulnerability disclosure deadlines in the context of AI-assisted vulnerability discovery and exploitation. Starting November 13, the team ended its 30-day patch roll-out grace period under a new 'Full X' policy, publishing flaw details 90 days after vendor notification regardless of whether a fix is released. The window drops to 60 days on February 2, 2027, and 30 days on January 3, 2028. Software vendors and users face tighter remediation schedules, as Project Zero only reports vulnerabilities with substantial severity and demonstrated impact.
Key Facts
| Attribute | Value |
|---|---|
| Disclosure date | November 13 (90-day disclosure; 30-day grace period removed), February 2, 2027 (60-day disclosure), January 3, 2028 (30-day disclosure), and 7-day window for flaws actively exploited in the wild |
How Is Google Project Zero Changing Its Disclosure Timeline?
Under its new 'Full X' policy, Google Project Zero ended its 30-day patch roll-out grace period starting November 13 and now discloses flaws 90 days after vendor notification regardless of fix status. The disclosure window will tighten to 60 days on February 2, 2027, and 30 days on January 3, 2028.
Previously, Project Zero gave software vendors 90 days to patch reported vulnerabilities before public disclosure, plus a 30-day grace period to roll out fixes. Project Zero security engineer Natalie Silvanovich announced the phased shift, noting that the team is also removing most 'special cases' from its disclosure rules.
From January 3, 2028, Google Project Zero will publicly disclose reported vulnerabilities 30 days after notifying the vendor, whether or not a patch is available.
Are Any Vulnerabilities Exempt From the Shorter Deadlines?
Project Zero is removing most special cases from its disclosure policy, though specific provisions remain. Security defects actively exploited in the wild still have a 7-day disclosure window under Google's policy, and flaws already made public by others remain outside the standard schedule. Rare exceptions may also still be granted for serious vulnerabilities.
Silvanovich noted that Project Zero has previously granted rare exceptions for serious flaws such as Spectre and Meltdown, and that practice will not change. In addition, Project Zero may publish vulnerability details ahead of the deadline if a vendor requests early disclosure. Silvanovich also pointed out that a vulnerability's severity affects only its impact on users, not the likelihood that attackers will discover it.
Vulnerabilities actively exploited in the wild remain subject to a 7-day disclosure window, and rare exceptions for serious flaws such as Spectre and Meltdown remain in place.
Why Is Project Zero Shortening Its Disclosure Windows?
Project Zero is shortening its deadlines in the context of AI-assisted vulnerability discovery and exploitation. Its phased transition addresses concerns around unpatched user exposure, vendor capacity, and the risk of overlooking older, more severe bugs, while encouraging vendors to strengthen their remediation processes and infrastructure over a challenging but realistic schedule.
"We decided on a policy that encourages vendors to improve remediation time on a schedule that is challenging but realistic, with the hope that this will lead to vendors broadly improving their remediation processes and infrastructure in a way that eventually enables them to fix all reported vulnerabilities quickly."
Natalie Silvanovich, Google Project Zero security engineer
Silvanovich emphasised that Project Zero only reports defects with substantial severity and demonstrated impact, and holds its submissions to strict quality standards:
"It's also important to acknowledge that Project Zero holds itself to high standards with regard to the reproducibility, readability, reachability, and reported security impact of the vulnerabilities we report. This policy assumes bug reports are of this quality, and it is reasonable for vendors to treat low quality-bug reports differently."
Natalie Silvanovich, Google Project Zero security engineer
Project Zero stated that its phased 'Full X' policy is designed to encourage vendors to upgrade their remediation processes and infrastructure while maintaining high standards for bug report quality.
What Should You Do?
- Note that this announcement covers a disclosure policy change rather than a specific software vulnerability, so no vendor fix is available or required for a particular product.
- If you manage software development or vendor security response, review and improve your remediation processes and patching infrastructure ahead of the February 2, 2027 (60-day) and January 3, 2028 (30-day) deadlines.
- Ensure vulnerability triage workflows do not overlook older, more severe reported bugs when prioritising newly reported issues under shorter deadlines.
- Maintain clear triage criteria for incoming external bug reports based on reproducibility, readability, reachability, and demonstrated security impact, while treating low-quality reports appropriately.
- For Malaysian organisations and IT administrators preparing for faster public vulnerability disclosures, monitor vendor advisories closely and report suspected cyber incidents to Cyber999 (MyCERT) or scams to the National Scam Response Centre at 997.
Common Questions
When does Google Project Zero's 30-day disclosure deadline take effect?
Google Project Zero is phasing in the change under its 'Full X' policy. The 30-day grace period ended on November 13, leaving a 90-day disclosure window. The deadline drops to 60 days on February 2, 2027, and shrinks to 30 days on January 3, 2028.
Will Project Zero still grant disclosure exceptions for major vulnerabilities?
Yes, though most special cases are being removed. Project Zero may still grant rare exceptions for serious vulnerabilities, as it did with Spectre and Meltdown. Defects actively exploited in the wild retain a 7-day window, and flaws already made public by others remain exempt.
Does Project Zero still publish details if a vendor has not released a patch?
Yes. Under the 'Full X' policy, Project Zero will publish vulnerability details after the deadline expires, regardless of whether or when a vendor releases a fix. Project Zero may also publish details ahead of the deadline if a vendor requests early disclosure.
Sources and Methodology
This dispatch is based solely on the SecurityWeek report by Ionut Arghire. No external advisories, vendor pages, or additional documents were reviewed or verified.
$ ls -t news/ | head -5
$ ls ./tags
- #Vulnerabilities