EXPLAINER
Vulnerabilities public in 30 days: the new Project Zero and Anthropic deadlines next to the EU CRA clock
Google Project Zero since 13 November 2026, and Anthropic from 1 January 2027, are cutting the time before the flaws they find go public. For a manufacturer selling software in the EU, a public advisory will no longer mean a patch exists, while the Cyber Resilience Act already runs its own 24-hour clock.

In brief
- Project Zero moved to a “Full 90” rule on 13 November 2026: details go public 90 days after the report, patched or not. The window drops to 60 days on 2 February 2027 and to 30 days on 3 January 2028.
- Anthropic will disclose high and critical flaws after 30 days and all others after 45, for reports made from 1 January 2027; actively exploited flaws stay at 7 days.
- Since 11 September 2026, the Cyber Resilience Act has required manufacturers to report actively exploited vulnerabilities: early warning within 24 hours, full notification within 72 hours.
Coordinated disclosure is a waiting period. A researcher tells a vendor about a flaw, then holds the details back so a fix can ship. Two of the most prolific bug-hunting teams have just shortened that wait, both citing AI. For counsel at a company that sells software in the EU, the timeline below matters because it now runs alongside a statutory one.
2021: the “90 + 30” rule
Project Zero, Google's team that hunts serious flaws in widely used software, adopted “90 + 30” in 2021: up to 90 days to fix, plus 30 days of “soak time” so users could install the update. In practice, a public Project Zero advisory usually meant a patch had been out for weeks.
11 September 2026: the EU starts its own clock
The Cyber Resilience Act entered into force on 10 December 2024. Its reporting duties apply first. Since 11 September 2026, according to the Commission's page on reporting obligations, a manufacturer must report an actively exploited vulnerability in a product with digital elements in three steps:
- an early warning within 24 hours of becoming aware;
- a full notification within 72 hours;
- a final report no later than 14 days after a corrective measure is available.
Everything goes once through the Single Reporting Platform run by ENISA, the EU cybersecurity agency. The notice is addressed to the national CSIRT where the manufacturer has its main establishment, which then shares it with the CSIRTs of other countries where the product is sold. The trigger is active exploitation. The Commission's page does not mention publication by a researcher.
13 November 2026: Project Zero drops the link to the patch
In a post dated 13 November 2026, Natalie Silvanovich announced “Full X”: details are disclosed X days after the vendor is notified. Whether the vendor has patched no longer moves the date. X is 90 from that day.
Most special cases go, including the grace period. Three exceptions remain, according to the policy page: flaws exploited in the wild (7 days, under Google's general policy), flaws already made public by others, and early disclosure requested by the vendor. The same page records that exceptions for wider user harm were granted five times in 12 years.
The stated reason is volume. Project Zero says large language models let it find “several vulnerabilities a week” in targets where it once found a few a year, and that attackers can now work back from a patch to the bug almost at once. Soak time, in its view, no longer protects anyone.
For a legal team, the consequence is mechanical. An advisory can now land before the fix. Project Zero says it will still state whether a bug is fixed, but that statement is no longer a precondition.
16 November 2026: Anthropic grades by severity
Anthropic's Frontier Red Team published its own schedule three days later. For reports made from 1 January 2027: 30 days for high and critical flaws, 45 days for the rest, 7 days unchanged under active exploitation. Escalation to an outside coordinator after 15 days of silence, down from 30. Full technical details 30 days after a patch, down from 45.
The two policies diverge on severity. Anthropic uses it. Project Zero refuses to, arguing that severity does not change how likely an attacker is to find a bug. Anthropic also keeps room to negotiate for hard-to-deploy software, such as critical infrastructure. It also admits a backlog: some serious flaws reported more than 90 days ago are still undisclosed, and their maintainers get 30 more days. The post gives no count.
February 2027 to January 2028: the dates to diary
- 2 February 2027: Project Zero moves to “Full 60”.
- 11 December 2027: the CRA's main obligations apply, and open-source software stewards take on reporting duties, according to the Commission.
- 3 January 2028: Project Zero moves to “Full 30”.
More explainers on the same rules: the EU AI Act timeline after the 2026 delay, the French report on generative AI and vulnerabilities handed to the presidency on 10 November 2026 and how OpenAI's control room maps onto the AI Act.
No date yet
Neither post says whether other research teams will follow, nor how vendors that already miss 90 days will meet 30 by January 2028. Whether a public but unexploited flaw changes anything under the CRA is for the Commission's guidance to settle, not for these policies.
Frequently asked questions
Will Project Zero publish a vulnerability that has not been patched?
Yes. Under the policy announced on 13 November 2026, details go public a fixed number of days after the vendor is notified, whether or not a fix has shipped. Project Zero says it will still track and state whether a bug is fixed.
When do Anthropic's shorter disclosure deadlines apply?
To vulnerabilities reported to vendors and maintainers on or after 1 January 2027. Reports already in progress on that date keep their existing deadlines, according to Anthropic's post of 16 November 2026.
Does the Cyber Resilience Act set a deadline for researchers to publish flaws?
No. It places reporting duties on manufacturers. Since 11 September 2026, an actively exploited vulnerability must be reported through ENISA's Single Reporting Platform: early warning within 24 hours, notification within 72 hours, final report within 14 days of a fix.
Share this article
Primary sources
- Updating our coordinated vulnerability disclosure policy timelines — Anthropic (Frontier Red Team), published 16 November 2026 · accessed on
- Policy and Disclosure: 2026 Edition — Google Project Zero (Natalie Silvanovich), published 13 November 2026 · accessed on
- Vulnerability Disclosure Policy — Google Project Zero · accessed on
- Cyber Resilience Act - Reporting obligations — European Commission · accessed on
- Cyber Resilience Act — European Commission · accessed on
An article by the Rédaction Explications & Glossaire, published under the editorial direction of Bastien Hugon. Editorial method and use of AI



