Research · 5 min read
Project Zero is shortening the time vendors get before a bug is published
Google’s research team dropped the extra 30 days on November 13. The deadline is 90 days now, 60 days in February 2027, and 30 days in January 2028.

Google Project Zero said on November 13, 2026 that it is cutting the time a software maker gets before the team publishes the details of a vulnerability it has reported. The policy post, by Natalie Silvanovich, replaces a rule the team has used since 2021. BleepingComputer reported the change on November 16. The current written policy is on Project Zero’s disclosure page.
If you do not ship software, this does not ask you to change a password. It changes how fast a fix has to reach you after a researcher tells the vendor.
What changed
Since 2021, Project Zero has used what it calls “90 + 30.” A vendor had 90 days to fix a bug, plus another 30 days before the technical details were published, so the patch could reach people. The new rule is “Full X”: the details are published X days after Project Zero reports the bug to the vendor, whether or not a fix is out.
Starting with the November 13 post, X is 90. On February 2, 2027, it becomes 60. On January 3, 2028, it becomes 30. The team’s reason, in the post, is that AI-assisted discovery and exploitation have made the old timeline too slow. It is an argument about the threat, not a count of attacks that used a Project Zero report.
The team is also dropping most of the exceptions it used to allow, including a grace period and a separate rule for variants of a bug. The disclosure policy page keeps these:
- A vulnerability Project Zero believes is already being used against people in the wild follows Google’s shorter rule for those cases. The disclosure page says that deadline is 7 days.
- If someone else has already published the details, Project Zero may publish too, at its discretion.
- If the vendor that received the report asks Project Zero to publish, it will.
- Project Zero may wait longer when publishing the details is likely to harm a large number of users and a delay would reduce that harm. The page says these exceptions are rare, that they are recorded in public, and that five have been granted in the last 12 years.
The disclosure page’s examples are concrete. A fix that ships on day 47 is still described in public on day 90. A fix that ships on day 90 is described the same day. A bug that is never fixed is described on day 90 anyway. Within a week of the report, the team says it will publish the reference number, the vendor, the product, the report date and the deadline on its transparency page, before the technical details.
What this means for a person using the software
The details Project Zero publishes are enough for a skilled person to try the bug. That is the point of the deadline: a vendor that has not shipped a fix does not get to keep the bug quiet past the date. For everyone else, the practical effect is that the gap between “the vendor knows” and “the recipe is public” is now fixed, and it is scheduled to get shorter.
Google’s own threat team, in a separate update on November 16, argued that some intruders are already using tools that turn a published patch into an exploit attempt with less of a person in the middle. Project Zero’s policy is about its own disclosure clock. It is not a claim that those attacks have already used a Project Zero report. We covered the threat update on its own.
What you can do
- Install updates when the vendor ships them, especially for anything that faces the internet: the browser, the phone, the router, the office VPN. A 90-day clock, and a shorter one later, is a reason not to wait for a quarterly window if a fix is already out.
- If you maintain a product and Project Zero writes to you, the date in the report is the publication date, not a suggestion, unless the team grants one of the rare harm exceptions on its policy page. If someone else has already published the details, Project Zero may publish immediately, at its discretion, which can be before that date. The extra 30 days are gone. The transparency page will name the product before the details do.
- A public proof of concept is still untrusted code. The policy explains when Project Zero will publish. It does not ask you to run a demonstration you found on a forum.
- If you do not ship software, there is no setting to change today. The people who need the calendar are the vendors. Your step is the update they ship.
How Frame helps
Frame can also look up your verified emails in Have I Been Pwned’s breach database. This note is about a disclosure policy, not a new list of addresses. Frame doesn’t scan your devices for unpatched bugs.
Related coverage
- Google says some intruders are now letting agents find and use flaws: a threat update on the same AI-assisted attack trend, published three days after this policy.
- The FBI says attackers are using the ARTEX framework to speed up break-ins: one of the tools Google’s update names.
Sources
- Google Project Zero, Policy and Disclosure: 2026 Edition, November 13, 2026
- Google Project Zero, Vulnerability Disclosure Policy
- BleepingComputer, Google Project Zero cuts bug disclosures to 30 days amid AI threats, November 16, 2026
More stories
New posts, by email.
About once a month. Plain-language privacy notes, nothing else. I never share your address.


