Unbiased headlines. Facts, not spin.
Unbiased Headlines is an independently owned news organization. We bring you the facts, not opinions, written fresh from 110+ named sources. Sources linked so you can verify it yourself.
Google Project Zero Ends 30-Day Grace Period, Sets 30-Day Bug Disclosure Deadline for 2028

Google's Project Zero has dropped the disclosure policy it followed since 2021 and replaced it with a countdown that ends at 30 days.
The team announced the change in a Nov. 13 post. The old "90+30" rule gave vendors 90 days to fix a bug and another 30 days of "soak time" for the patch to reach users. That extra month is gone.
The new schedule
Project Zero calls the new policy "Full X," where X is the number of days between reporting a bug to a vendor and publishing the technical details. It starts as Full 90. On Feb. 2, 2027, it becomes Full 60. On Jan. 3, 2028, it becomes Full 30.
Publication happens on the deadline whether or not a fix exists. The grace period and the variant policy are also removed. Project Zero will still track whether bugs get fixed, but fix status no longer decides when details go public.
Three exceptions remain. Bugs actively exploited in the wild, bugs whose details are already public, and cases where the vendor asks for earlier publication can all be disclosed sooner. Project Zero also says it may hold back in rare cases, citing Spectre and Meltdown, which it withheld for more than 120 days.
Why Project Zero says it did it
Project Zero blames AI, specifically large language models. Natalie Silvanovich of the team wrote that a vulnerability reported today poses a much higher immediate risk to users than one reported a year ago, because more parties, including malicious ones, are likely to find the same bug while it sits under embargo.
The team also says models shrink the time it takes to turn a patch into a working exploit. It now treats zero patch-to-exploitation time as a reasonable, if imperfect, model of attacker behavior. A patch tells attackers where the bug is, and the team argues that waiting a month to publish gives users a false sense of secrecy.
Then there is volume. "We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year," Project Zero said. Negotiating over whether a bug is fixed or a grace period applies is "quickly becoming unmanageable," Silvanovich wrote.
Severity will not move the date either. Project Zero argues a bug's severity changes its impact on users, not the likelihood attackers find it.
Vendors pushed back
Project Zero consulted vendors before settling on the phased approach. Google said they warned that going straight to 30 days could hurt users by exposing unfixed bugs while vendors are still upgrading their remediation processes. Vendors also warned it could push maintainers to fix Project Zero's reports ahead of more severe flaws reported by others, or lead some to stop trying.
Google's answer: "While the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period, we still feel there are benefits in the short term." The gradual schedule is meant to give vendors time to build faster fix pipelines.
Ivan Milenkovic, VP of risk technology at Qualys, told Infosecurity Magazine that Project Zero had "removed the snooze button on responding to issues." He said the finding rate describes "an arrival rate that most patch programmes were never built for," and that an organization patching monthly is now slower than disclosure. He called the vendors' objection "a fair response, but the alternative was letting attackers set the deadline."
Anthropic moves in the same direction
Today, Nov. 16, Anthropic's Frontier Red Team announced its own tightening. It will publish high- and critical-severity flaws 30 days after reporting, down from 90. All other flaws get 45 days.
The new deadlines apply to flaws reported on or after Jan. 1, 2027. Reports already in progress keep their old terms. Anthropic also said it will escalate to an outside coordinator after 15 days of maintainer silence instead of 30, and wait 30 days after a patch ships before releasing full technical details, down from 45.
Some serious flaws Anthropic reported more than 90 days ago are past its current deadline and still not public. Anthropic says it is giving those maintainers 30 more days, then will publish them on its dashboard.
"A 90-day window made sense when a vulnerability could be expected to stay private for months. We no longer believe it can," Anthropic wrote. Its seven-day window for flaws under active attack is unchanged. Where a fix legitimately takes longer, such as critical infrastructure software or a technical standard, Anthropic says it will agree a timeline with the vendor.
Anthropic acknowledged that shorter deadlines may put more pressure on maintainers, and said it will keep sending fix guidance, and a patch where it can, with each report. The policy does not cover AI findings no person has reviewed, such as output from its OSS Scanner service.
What comes next
Project Zero is not a regulator. It has no legal power over any vendor. What it has is the ability to publish, and that now arrives on a calendar.
The first hard test is Jan. 1, 2027, when Anthropic's new terms take effect for reports filed from that date, followed by Feb. 2, 2027, when the Project Zero window falls to 60 days. Whether vendors can ship fixes at that pace, or whether unpatched bugs start appearing in public, is still unanswered.
Sources used for this briefing
6 links from 6 independent newsrooms (syndicated copies of the same report count once)
These are the sources it draws on, linked so you can verify.