← Back to Technomalist
Cybersecurity/news/3 min read

Google Project Zero Tightens Vulnerability Disclosure Clock in Three Steps

Project Zero is phasing out its 90-day-plus-30-day disclosure model, with fixed deadlines shrinking to 60 days in 2027 and 30 days in 2028. The source does not identify a specific vulnerable product or patch.

Featured image for Google Project Zero Tightens Vulnerability Disclosure Clock in Three Steps
Featured image for Google Project Zero Tightens Vulnerability Disclosure Clock in Three Steps

Google’s Project Zero research team is changing how long it waits before publishing technical details about serious security flaws, according to BleepingComputer. The team will replace its “90+30” model with shorter fixed deadlines, reflecting concern that AI is speeding up both vulnerability discovery and exploitation.

Confirmed policy changes

The transition is already under way. BleepingComputer reports that the 30-day extension was removed from the disclosure timeline on November 13. On February 2, 2027, the deadline is scheduled to fall to 60 days. On January 3, 2028, it is set to drop to 30 days.

When a deadline expires, Project Zero will publish vulnerability details even if a fix is not ready. That is the central tension in the policy: vendors get less time to investigate, develop patches, and distribute them before technical information becomes public.

Project Zero is Google’s vulnerability research unit, known for finding flaws in widely used software and hardware. BleepingComputer cites recent work including a .NET Framework zero-day, issues in Chrome’s JavaScript and graphics components, and a Qualcomm chipset zero-day linked to NoviSpy spyware activity. The report does not identify a current flaw, affected product, or available patch tied to the disclosure-policy change.

Why Google is acting

According to the report, Project Zero says AI has made vulnerability discovery and exploitation faster. It also says attackers can more easily reverse-engineer fixes once patches ship and turn that knowledge into working exploits. That reduces the protective value of a long embargo, in Google’s view.

The team chose a gradual schedule rather than moving directly to 30 days. BleepingComputer reports that vendors warned Google that an immediate shift could put users at risk and could lead maintainers to concentrate on Project Zero reports while missing other serious flaws. Google said the gradual approach gives vendors time to improve flaw management and remediation systems, while acknowledging that the short-term benefits of delaying disclosure are declining.

Project Zero also retains exceptions. Early disclosure may occur when a flaw is already exploited in the wild, when exploitation or vulnerability details have already been published elsewhere, or when a vendor asks for it. Google also says it can withhold disclosure when it deems necessary, citing Spectre and Meltdown as an example where information was held for longer than 120 days.

Who is affected, and what to do now

The policy change does not point to a specific product that users need to patch. Instead, it affects the disclosure process around flaws in widely used software and hardware. Vendors covered by Project Zero research face stronger pressure to investigate reports and ship fixes faster. Defenders should treat the change as a signal that technical details may become public sooner, but the source provides no product-specific remediation step.

Interpretation

The practical effect is likely to be procedural: vendors have a narrowing window to fix serious flaws before details appear. Whether the shorter deadlines improve security overall depends on how quickly vendors adapt, a question the source does not resolve. The report establishes Google’s policy direction and vendor concerns; it does not demonstrate that the new deadlines have already reduced harm or caused specific breaches.

REPORTING NOTES

Sources and further reading

See an error? Read our corrections policy or email [email protected].

MORE FROM TECHNOMALIST

Continue reading

View all ↗