Google Project Zero Ends 90+30 Grace Period: What Fixed 90-60-30 Day Disclosure Means for IT and SaaS Buyers
Advertisement
What happened
Google Project Zero, the company's vulnerability research team, announced a new vulnerability disclosure policy on November 13, 2026, and published the full details in its official blog post titled Policy and Disclosure: 2026 Edition. Vulnerabilities will be disclosed a fixed number of days after they are reported to the vendor, whether or not a patch exists.
Since 2021, the team has used a 90+30 model: up to 90 days for a vendor to fix a bug, plus 30 days of "soak time" for users to install the patch. Help Net Security reported on November 16 that the new approach, called Full X, removes the 30-day grace period and its variant policy.
The schedule
- From November 13, 2026: Full 90, with disclosure 90 days after the report.
- From February 2, 2027: Full 60.
- From January 3, 2028: Full 30.
Exceptions that remain
Actively exploited vulnerabilities fall under Google's application security disclosure policy. Project Zero may publish its own details if others already made a bug public, will publish if the vendor asks, and will rarely extend time for hardware flaws such as Spectre and Meltdown. Severity ratings and negotiation over whether a bug is fixed no longer decide the date.
Why Project Zero says it is changing
Project Zero's stated reason is AI-assisted vulnerability discovery and exploitation. The team says attackers can now derive bug details from a patch almost immediately, raising the chance that several parties, including malicious ones, find the same flaw during an embargo.
It also says the old grace period no longer protects users and can create a false sense of secrecy, and that finding several vulnerabilities a week has made case-by-case negotiation unmanageable. Vendors had raised concerns that abrupt deadlines might push teams to prioritize Project Zero's bugs over more severe ones, which is why the shorter windows phase in gradually.
Why it matters for B2B software buyers
The change shrinks the time between a bug report and public technical detail. For IT and security teams, that means the window in which a known flaw is unpublished and unpatched is getting shorter, and unpatched products may appear with public details sooner.
Project Zero reports bugs in widely used products from many vendors, so effects reach operating systems, browsers, cloud components and enterprise software. Buyers cannot assume that "reported but not yet public" means safe. Two practical consequences follow:
- Patch gap becomes a vendor-quality metric. The time from fix to customer installation matters as much as time to fix.
- Vendor patch SLAs deserve scrutiny. A vendor that cannot ship fixes inside 60 or 30 days will see bug details published unpatched.
Exposure also compounds when exploited flaws are tracked in public catalogs. Our report on a Check Point Gaia vulnerability added to the CISA catalog shows how quickly exploited bugs move from disclosure to active attacks.
What IT teams should do now
Treat shorter disclosure windows as a prompt to tighten your own patching and vendor oversight. You do not need new tooling to start, only clear targets, current inventories and contract language that matches the new pace.
- Set internal patch targets for critical and internet-facing systems in days, not weeks, and measure compliance.
- Keep an accurate software and SaaS inventory so you can find affected products quickly when details are published.
- Ask vendors for their vulnerability response and patch delivery commitments, and add them to renewal checklists.
- Subscribe to vendor security advisories and the CISA Known Exploited Vulnerabilities catalog, then route alerts to your ticketing system.
- Test patches in a staging ring so you can deploy quickly without breaking production.
Related SaaSPodium categories
Security and IT teams that want to review their exposure and speed up patching can compare dedicated tools in the SaaSPodium directory, starting with Vulnerability Management Software and Patch Management Software. For scanning options, see our comparison of network vulnerability scanners.
This story is developing as vendors respond. SaaSPodium will cover material follow-ups, and readers should check the Project Zero policy page for the authoritative wording and dates.
Frequently Asked Questions
What is Google Project Zero's new Full X policy?
Full X means vulnerability details are published X days after the report to the vendor. X is 90 days now, 60 days from February 2, 2027, and 30 days from January 3, 2028, with limited exceptions.
Does the change affect my patching schedule?
Indirectly. Shorter windows mean public technical details may appear sooner, so prioritize internet-facing and critical systems, shorten your patch cycles and ask vendors about their fix delivery times.
Which vendors are affected by the policy?
Any vendor whose products Project Zero reports bugs in, which spans operating systems, browsers, cloud and enterprise software. Review each vendor's security response commitments at your next renewal.
Advertisement