Google will soon drastically reduce the disclosure deadlines of vulnerabilities prior to publicly disclosing them, and the move has sparked concern among some cybersecurity professionals.
Project Zero, Google’s third-party vulnerability remediation program, currently follows what it describes as “90+30” policy: 90 days to remediate a vulnerability and an extra 30-day “soak time” to allow for patch rollout before publicly disclosing the bug. This will no longer be the case. As of the announcement on Nov. 13, Google changed its policy to disclose 90 days after reporting to the vendor. As of Feb. 2, 2027, vulnerabilities will be disclosed after 60 days. As of Jan. 3, 2028, vulnerabilities will be disclosed after 30 days.
In a blog post outlining the decision, Google’s Natalie Silvanovich wrote that while the intention of 90+30 was to encourage faster patching while giving vendors time to deliver patches, “The advent of AI-assisted vulnerability discovery and exploitation has changed the threat landscape such that the vulnerability remediation timeline encouraged by our disclosure policy is clearly insufficient.”
Specifically, Silvanovich noted that large language models have enabled threat actors to find and exploit vulnerabilities much faster in today’s AI era.
“A vulnerability reported today presents a much higher immediate risk to users than one reported last year. In this new environment, it is crucial that vendors move towards remediating vulnerabilities faster,” she wrote. “LLMs have also decreased the time it takes for attackers to reverse engineer and exploit a vulnerability based on a patch, to the extent that zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior.”
Project Zero is not a conventional bug disclosure program. Founded in 2014, the organization was established specifically so Google could help facilitate the safe reporting and disclosure of high-severity, high-impact vulnerabilities found in widely used software and hardware. That said, Project Zero’s move reflects a broad inundation of AI-discovered vulnerabilities, and where Google goes, the rest of the industry may follow.
As for whether such a thing is good, bad, or necessary for the cybersecurity industry, experts appear to be split.
Vulnerability Disclosure: An Imperfect Science
Disclosure timelines are a key part of the vulnerability ecosystem. When a researcher or firm discovers a vulnerability and submits it to the software developer responsible, a standard timeline is usually designated for the developer to fix the vulnerability; such deadlines are usually 90 or 120 days, but it varies depending on the bug, disclosure policy, and circumstances.
If the software developer ignores the bug report, is slow to address it, or declines to communicate with the researcher, the researcher may choose to disclose the flaw at the end of the disclosure timeline to inform security teams and practitioners of the looming threat. These timelines hold software vendors accountable and encourage them to maintain secure software, but it’s not perfect science.
Oftentimes, the researcher and software developer will work together to coordinate a disclosure date so relevant research, patches, and mitigations are ready at the same time. Sometimes, if the bug is especially dangerous or requires more time to fix, the timeline may change and the technical details and proof-of-concept exploits will be held until a later date.
It’s worth noting there are no standard requirements between platforms. HackerOne keeps its default disclosure timeline to 30 days, though it’s broadly set at the program level by each vendor customer, and many HackerOne programs set longer timelines. Bugcrowd researchers and vendors generally coordinate timelines; program rules again supersede standards.
TrendAI’s Zero Day Initiative (which is not a platform but a vendor-agnostic vulnerability disclosure program) uses a standard disclosure timeline of 120 days for responsive vendors that release working patches, and shorter timelines for vulnerabilities that result from faulty patches.
It remains to be seen whether the larger industry will follow Project Zero’s lead. Dustin Childs, ZDI’s head of threat awareness, calls Google’s decision “a bold move to be sure, especially considering the explosion of bug reports coming in thanks to AI assisted discovery.”
However, he worries about how shorter timelines may impact remediation quality. “I fear it will lead to patches that don’t fully address the vulnerability. We see that happen at 120 days,” Childs says. “We’ll be watching closely to see how this change impacts vendors and researchers alike.”
Alex Rice, cofounder, CISO, and CTO at HackerOne, tells Dark Reading that he expects the industry to move in Google’s direction, though not necessarily in lockstep. He argues that patch soak time no longer protects defenders, given how quickly attackers can exploit flaws now. And because Project Zero is a disclosure program for vulnerabilities with demonstrated impact and not a bug bounty platform that addresses a broad range of flaws, Google is in a unique position to set aggressive expectations.
“The specifics will still vary by program, severity, and whether a fix is realistic, and platforms like ours will need to support that flexibility,” Rice says. “But the direction isn’t in question. Organizations should plan for 30 days as the baseline expectation that will shrink even further.”
How Will Organizations Keep Up With Shorter Deadlines?
Between stories from this year about AI models capable of discovering zero-day bugs off of human language prompts and vulnerability coordinators fighting huge spikes in bug reporting volumes the past couple of years, Google’s position seems defensible. The tech giant isn’t alone in its move either: In January, Anthropic’s own coordinated disclosure policy will shorten from 90 days to 30 days for high- and critical-severity bugs, and 45 days for all other cases.
But not everyone agrees. Expel principal threat researcher Marcus Hutchins took issue with the move in a post to X, where he noted that 2026 has already seen far more CVEs than 2025. “Sure, there are some vendors who just sit on bugs forever and don’t make any effort to patch them. But there’s way more overworked & underpaid teams, non-profits, and solo projects who are patching bugs as fast as they physically can,” he wrote.
Katie Moussouris, CEO of Luta Security and a pioneer in vulnerability disclosure, largely agrees. As she tells Dark Reading, even AI firms currently struggle to patch the issues they find, leaving volunteers and less resourced firms even further back against the wall. “A deadline doesn’t magically manifest a fix.”
“Researchers and AI companies are burying maintainers in bug reports and not doing enough to help fix them. This isn’t even a matter of model access or token cost. The AI companies themselves can’t even close the gap,” she says. “Anthropic reports that 629 of the 5,087 vulnerabilities it disclosed have been patched. OpenAI’s Patch the Planet initiative, run with security engineers from Trail of Bits, has written patches for a third of the 2,055 issues it found, and 23% have been accepted upstream.”
A Google spokesperson tells Dark Reading that in creating the new policy, the company solicited feedback from the vendors Project Zero reports the most vulnerabilities to, including open source projects.
“The general consensus was that these timelines are achievable, and most open source projects are almost there,” the spokesperson says. “Every vulnerability that Project Zero reported against a volunteer-maintained project in 2026 was fixed in 30 days, except for one, which was fixed in 31 days. Open source projects are among the vendors who will need to make the fewest changes to meet our new policy, as they are already doing so well.”
Shorter Disclosure Timelines May Be Inevitable
While one side of the argument disagrees with the rollout of shorter timelines, the other side sees it as inevitable or necessary to respond to how attackers now use AI to pursue their goals. HackerOne’s Rice says that right now, teams are not ready to deal with a 30-day turnaround, but Google’s move may offer an opportunity at the boardroom level to convince technology and executive partners that remediation is a shared responsibility.
“If you’re a security team struggling to keep up, don’t waste time playing the victim. Take this as a gift,” he says. “Ask for dedicated engineering capacity for security fixes, pre-agreed remediation SLAs, automated validation and retesting, and the authority to ship mitigations while the full fix is built. The teams that turn this pressure into that conversation will be far ahead of the ones hoping for external relief.”
Casey Ellis, founder of Bugcrowd and The disclose.io Project, says this is a necessary evolution, even if it feels aggressive. In the wake of proliferated vulnerability discovery, the timeline shortening “puts productive pressure on response and fix pipelines.”
Ellis says he feels the typical targets of Project Zero researchers are in “decent shape,” but community norms tend to follow Google’s lead on CVE timelines, so the move could carry larger impact.
“My main concern would be companies that maintain safety-critical systems or those that are otherwise logistically difficult to update; a security fix doesn’t always end with a patch, and more often than not, it doesn’t,” he says. “The Project Zero changes will ultimately reveal (and hopefully shrink or close) the readiness gap for many PSIRT teams, products, and hosted service providers, but unless product vendors become proactive about this aspect of vulnerability discovery and disclosure it is likely to be a bumpy ride for some.”

No responses yet