Science & Tech · Cybersecurity · 2 hrs ago
Google Project Zero to cut vulnerability disclosure deadline to 30 days by 2028
Google’s Project Zero is shortening its deadlines for disclosing software security flaws after reporting them to vendors.
Under the new policy, it will publish details after 90 days, whether or not the vendor has released a fix.
The deadline will drop to 60 days on February 2, 2027, and to 30 days on January 3, 2028.
The change ends the extra 30-day period previously allowed for patches to reach users after a fix was made.
Project Zero says AI is helping attackers find flaws and turn patches into exploits faster, making delayed disclosure less protective.
Vendors warned that shorter deadlines could expose users to unfixed flaws or divert attention from other serious bugs, so the change is being phased in.
The shorter deadlines are intended to push vendors to fix flaws and get updates to users faster, while some exceptions will remain, including for flaws already being exploited.
Google Project Zero is replacing its “90+30” vulnerability disclosure policy with fixed, shorter deadlines.
Under the new policy, it will publish vulnerability details 90 days after reporting them to a vendor, whether or not a fix is available.
The deadline will fall to 60 days on February 2, 2027, and to 30 days on January 3, 2028.
Project Zero says AI is speeding up vulnerability discovery and exploitation, reducing the value of delaying disclosure.
Vendors warned that faster disclosure could expose users to unfixed vulnerabilities or divert attention from other serious flaws.
- Who
- Google Project Zero, Google’s vulnerability research team, is changing its disclosure policy. Vendors that receive its vulnerability reports are affected.
- What
- Project Zero is moving to fixed disclosure deadlines, starting at 90 days and eventually reaching 30 days. It will publish details even if a fix is not available.
- When
- The transition began on November 13, 2026. The deadlines change on February 2, 2027, and January 3, 2028.
- Where
- Not stated
- Why
- Project Zero says AI-assisted discovery and exploitation have made vulnerabilities easier and faster to find and exploit. It wants vendors to improve remediation and patch delivery.
Google Project Zero
Vendors consulted by Project Zero
Disclosure timing
Google Project Zero
Project Zero says shorter fixed deadlines reflect the reduced value of delaying disclosure as attackers can find vulnerabilities or reverse-engineer patches faster.
Vendors consulted by Project Zero
Vendors warned that immediate disclosure changes could expose users to unfixed bugs and lead them to prioritize Project Zero reports over potentially more severe flaws.
Project Zero began the transition by removing the 30-day grace period from its disclosure timeline.
Project Zero’s disclosure deadline is scheduled to fall to 60 days after reporting a vulnerability.
Project Zero’s disclosure deadline is scheduled to fall to 30 days after reporting a vulnerability.
- Initial deadline
- 90 days after reporting a vulnerability
- Previous policy
- 90+30” days, including a 30-day patch rollout grace period
- Next deadline change
- 60 days on February 2, 2027
- Final deadline change
- 30 days on January 3, 2028
- Policy name
- Full X
- Stated driver
- AI-assisted vulnerability discovery and exploitation
5 sources
Google Project Zero Slashes Bug Disclosure Deadlines, Splitting Experts
Google Project Zero cuts bug disclosures to 30 days amid AI threats
Google Project Zero Sets Course for 30-Day Disclosure Deadline
Google Project Zero to Cut Disclosure Deadline to 30 Days by 2028
Google Project Zero will disclose bugs after 90 days, fixed or not
What people are saying
We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year.
An overarching concern was that immediately changing the policy could harm users by making unfixed vulnerabilities available to attackers while vendors are in the process of improving their remediation processes and technology.
We decided on a policy that encourages vendors to improve remediation time on a schedule that is challenging but realistic, with the hope that this will lead to vendors broadly improving their remediation processes and infrastructure in a way that eventually enables them to fix all reported vulnerabilities quickly.
This describes an arrival rate that most patch programmes were never built for.