---
slug: "ai-project-zero-30-523528bf"
title: "Responding to the AI vulnerability discovery challenge: Google Project Zero plans to gradually shorten the public vulnerability disclosure period to 30 days."
headline: "Responding to the AI vulnerability discovery challenge: Google Project Zero plans to gradually shorten the public vulnerability disclosure period to 30 days."
canonical: "https://silinex.xyz/wire/ai-project-zero-30-523528bf"
date_published: "2026-11-15T10:12:07.000+00:00"
date_modified: "2026-11-15T10:20:39.237+00:00"
author: "IT之家"
publisher: "Silicon Nexus"
category: "ai"
summary: "Compiled from public reports including IT之家: Since 2021, Google's vulnerability-hunting program Project Zero has followed a \"90 + 30\" disclosure policy, allowing vendors up to 90 days to fix a vulnerability and provid…"
signal_type: "other"
impact_score: 0
tldr:
  - "IT Home, November 15: Since 2021, Google's vulnerability hunting program Project Zero has followed a \"90 + 30\" disclosure policy, which allows vendors up to 90 days to fix a vulnerability and provides an additional 30-day \"grace period\" for patch rollout."
  - "On November 13 local time, Google announced that with the rise of AI-assisted vulnerability discovery and exploitation techniques, the current situation has fundamentally changed, and the remediation periods set by existing disclosure policies can no longer meet the demand."
  - "IT Home has learned that in order to encourage vendors to fix vulnerabilities more quickly and to push them to shorten the \"patch gap,\" Google has released a new vulnerability disclosure policy. Under the new policy, regardless of whether a vendor has completed a fix, vulnerabilities will be publicly disclosed X days after being reported to the vendor, with the time limit gradually tightened in stages."
entities:
  []
key_metrics:
  []
key_facts:
  - "IT Home, November 15: Since 2021, Google's vulnerability hunting program Project Zero has followed a \"90 + 30\" disclosure policy, which allows vendors up to 90 days to fix a vulnerability and provides an additional 30-day \"grace period\" for patch rollout."
  - "On November 13 local time, Google announced that with the rise of AI-assisted vulnerability discovery and exploitation techniques, the current situation has fundamentally changed, and the remediation periods set by existing disclosure policies can no longer meet the demand."
  - "IT Home has learned that in order to encourage vendors to fix vulnerabilities more quickly and to push them to shorten the \"patch gap,\" Google has released a new vulnerability disclosure policy. Under the new policy, regardless of whether a vendor has completed a fix, vulnerabilities will be publicly disclosed X days after being reported to the vendor, with the time limit gradually tightened in stages."
---
# Responding to the AI vulnerability discovery challenge: Google Project Zero plans to gradually shorten the public vulnerability disclosure period to 30 days.

## Silicon TL;DR

1. IT Home, November 15: Since 2021, Google's vulnerability hunting program Project Zero has followed a "90 + 30" disclosure policy, which allows vendors up to 90 days to fix a vulnerability and provides an additional 30-day "grace period" for patch rollout.
2. On November 13 local time, Google announced that with the rise of AI-assisted vulnerability discovery and exploitation techniques, the current situation has fundamentally changed, and the remediation periods set by existing disclosure policies can no longer meet the demand.
3. IT Home has learned that in order to encourage vendors to fix vulnerabilities more quickly and to push them to shorten the "patch gap," Google has released a new vulnerability disclosure policy. Under the new policy, regardless of whether a vendor has completed a fix, vulnerabilities will be publicly disclosed X days after being reported to the vendor, with the time limit gradually tightened in stages.

## Wire brief

Compiled from public reports including IT之家: Since 2021, Google's vulnerability-hunting program Project Zero has followed a "90 + 30" disclosure policy, allowing vendors up to 90 days to fix a vulnerability and providing an additional 30-day "buffer period" for patch rollout.

In terms of the timeline, on November 13 local time, Google announced that with the rise of AI-assisted vulnerability discovery and exploitation techniques, the situation has fundamentally changed, and the remediation periods set by the existing disclosure policy can no longer meet demand. IT之家 has learned that, to push vendors to fix vulnerabilities more quickly and to encourage them to shorten the "patch gap," Google has issued a new vulnerability disclosure policy. Under the new policy, regardless of whether a vendor has completed a fix, a vulnerability will be publicly disclosed directly X days after being reported to the vendor, with the time limit tightened in stages. From November 13, 2026, the original 30-day patch buffer period will be abolished, and disclosure will occur 90 days after reporting; from February 2, 2027, disclosure will occur 60 days after reporting; from January 3, 2028, disclosure will occur 30 days after reporting. At the same time, Google will remove the vast majority of "special circumstances" from the disclosure policy. The new policy retains only the following three exceptions, under which disclosure will not wait for the full X days: vulnerabilities exploited in the wild (ITW): vulnerabilities already actually exploited by attackers will continue to follow Google's application security vulnerability disclosure policy; already public vulnerabilities: if vulnerability details have already been publicly disclosed by others in advance, Project Zero may at its discretion disclose detailed information about the vulnerability.

Public information also mentions: at the vendor's request: if the vendor receiving the vulnerability report proactively makes a request, Google will disclose the vulnerability details.

Silicon News Wire only rewrites and polishes the key points; the complete wording and context are subject to the original page.

---

Source desk: **IT之家** · [origin link](https://www.ithome.com/1/027/423.htm)
