Vulnerability disclosure policy of Google Project Zero moves to Full 90, 60 and 30

Google Project Zero has announced a new vulnerability disclosure policy. Project Zero finds security flaws and reports them to vendors, the companies that make the software. Since 2021 it allowed vendors 90 days to fix a flaw, plus 30 extra days of “soak time” for patch rollout.

According to Project Zero, AI-assisted vulnerability discovery has made that timeline clearly insufficient. Large language models (LLMs) help attackers find and exploit bugs faster. They also raise the risk that several parties, including malicious ones, find the same bug.

LLMs also shorten the time needed to turn a patch into an exploit. Project Zero says zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behaviour. Soak time therefore no longer helps and can create a false sense of secrecy.

The “patch gap” is the time between a fix being released and the user installing it. Project Zero wants vendors to shrink it, either by faster rollout or by other ways to protect users. The team also finds several vulnerabilities a week where it once found a few a year, so negotiating each case is becoming unmanageable.

The new policy is called “Full X”, and vulnerabilities are disclosed X days after they are reported. Today it is “Full 90”. On February 2, 2027 it becomes “Full 60”, and on January 3, 2028 “Full 30”.

Most special cases are gone, including the grace period and variant policy. Three exceptions remain. Actively exploited vulnerabilities follow Google’s application security disclosure policy, public vulnerabilities may be published at Project Zero’s discretion, and details are released when the vendor asks for it.

Why the gradual schedule? Vendors told Project Zero that an immediate change could expose unfixed bugs to attackers while they improve their processes. They also feared that less severe bugs would get priority, or that vendors would give up on deadlines they cannot meet. The schedule is meant to be challenging but realistic.

Project Zero will still track whether bugs are fixed, but this is no longer a decision point. Severity does not decide disclosure either, because it does not change how likely attackers are to find a bug. For your organisation, the message is clear. Expect shorter windows between a report and public details, and apply updates quickly.

Read projectzero.google article for more information.

Previous Post

Microsoft 365 outage resolved as Microsoft rules out a cyberattack

Next Post

Smart glasses privacy and the problem of recording everyone around you

Related Posts