"We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year," Project Zero wrote on November 13, announcing a decisive change to how it will publish technical details about software flaws.
Project Zero's Full X policy
Google's Project Zero has replaced its long-standing "90 + 30" disclosure policy with a new framework it calls Full X. Under Full X, Project Zero will publish vulnerability details X days after reporting them to vendors — irrespective of whether a patch or mitigations exist. The group removed the 30-day "soak time", the grace period and the variant policy. It also said it will continue to track whether bugs are fixed, but "fix status would no longer decide when technical details are published."
Timeline: Full 90, then Full 60, then Full 30
The policy begins as Full 90, meaning publication 90 days after reporting. Project Zero will move to Full 60 on February 2, 2027, and reach Full 30 on January 3, 2028, at which point vulnerabilities will be disclosed 30 days after reporting. Three narrow exceptions remain: vulnerabilities actively exploited in the wild, bugs whose details have already been made public, and cases where vendors ask Project Zero to publish the details.

This site is the portfolio.
OSINTSights runs on Cloudflare Workers, D1, R2, and Vectorize, with an AI pipeline on Hetzner ARM. Nubivance designed, built, and operates it. We do the same for clients.
See what we buildTied to AI-assisted discovery and rapid patch-based inference
Project Zero explicitly linked the change to developments in automated and AI-assisted vulnerability discovery and exploitation. The group argued that "soak time" was no longer meaningful because attackers can almost immediately work out bug details from a patch. Project Zero also stated that severity should not determine disclosure timing, writing that "a vulnerability's severity does not affect the likelihood that it will be discovered by attackers, only its impact on users."
Vendors' warnings and defenders' response
Vendors consulted by Project Zero warned that an abrupt shift to faster disclosure could expose unfixed bugs, push them to prioritize fixes for Project Zero reports ahead of more severe issues, or even lead some vendors to stop engaging with the researcher group. Defenders pressed by the change framed the problem as an operational tempo mismatch. Ivan Milenkovic, vice president of risk technology at Qualys, told Infosecurity that Project Zero had "removed the snooze button on responding to issues." He added that the group's finding rate "describes an arrival rate that most patch programmes were never built for," and warned that "patching monthly now means you're slower than disclosure." Still, he called vendors' objection "a fair response, but the alternative was letting attackers set the deadline."
How technologists, vendors, and organizations are responding
- Technologists and security teams: They will be pressed to shorten the "patch gap" — the period between a fix becoming available and users installing it — because Project Zero said its new policy is intended to encourage vendors to reduce that gap.
- Vendors: Some warned an immediate change could expose unfixed bugs, skew prioritization toward Project Zero findings, or discourage engagement; the policy nonetheless allows vendors to ask Project Zero to publish details in specific cases and preserves exceptions for active exploitation and already-public bugs.
- Organizations and IT operations teams: The change raises an operational constraint for groups that patch on monthly cadences, which Project Zero and defenders say will now be slower than disclosure timelines under Full X.
Project Zero's shift reframes disclosure timing as a tool to compress the interval between vulnerability discovery and remediation rather than a lever to delay public technical details until patches exist. It narrows the set of circumstances that will pause publication to active exploitation, prior public disclosure, or explicit vendor requests — and it sets a clear deadline march: 90 days now, 60 days in February 2027, and 30 days in January 2028. Whether vendors and large-scale patch programs can accelerate enough to match that march, or whether the exceptions and vendor engagement will alter the practical effect, remains the immediate operational question.




