RSS
News

Anthropic moves to 30-day bug disclosure for high-severity reports, three days after Project Zero dropped 90+30

For vulnerabilities it reports on or after January 1, 2027, Anthropic will disclose high- and critical-severity bugs after 30 days and all others after 45, down from 90. Google Project Zero has moved to a fixed 90-day clock that steps down to 60 and then 30 days.

A black cable is wrapped around a metal pole
Photo by Andy Kennedy on Unsplash

Anthropic is shortening the deadlines in its coordinated vulnerability disclosure (CVD) policy. The policy covers bugs Anthropic finds in open-source software, and in closed-source software it is authorized to test: Claude models find candidate vulnerabilities, and external security firms triage and validate most of them before they are reported. In a November 16, 2026 post from its Frontier Red Team, Anthropic said the disclosure window will drop from 90 days to 30 days for high- and critical-severity issues, and to 45 days for all other issues. The new timelines apply to vulnerabilities reported to vendors and maintainers on or after January 1, 2027; reports still in progress on that date keep their existing deadlines.

The change comes three days after Google Project Zero retired its own 90+30 policy on November 13. Both point to AI. Anthropic says models can now help develop fixes and that a bug one model can find is increasingly likely to be found by another, so it is seeing more rediscovery. Project Zero says LLMs have increased the speed at which attackers can find and exploit vulnerabilities, and that attackers can now work out bug details from a patch almost immediately.

What changes in Anthropic's policy

  • Disclosure window: 30 days for high and critical severity, 45 days for all other severities (both were 90), for reports sent on or after January 1, 2027.
  • No response from the maintainer: Anthropic will aim to escalate to an external vulnerability coordinator after 15 days instead of 30.
  • After a patch ships: Anthropic will wait 30 days instead of 45 before sharing full technical details. The current policy says that buffer can be shortened if details are already public, or extended when patch deployment is unusually complex or broad.
  • Unchanged: the 7-day window for vulnerabilities under active exploitation, and, Anthropic says, the rest of the policy.
  • Not covered: AI-discovered findings that have not had human review, such as reports from Anthropic's OSS Scanner service.
  • Hard cases: for flaws in hard-to-deploy software such as critical infrastructure, or flaws that need a specification or RFC change, Anthropic says it will work with the vendor on a remediation timeline.

Two parts of the existing policy matter more under a shorter clock. It already allows a 14-day extension on request when a maintainer is engaged and making progress near the deadline; the November 16 post does not say how that extension combines with the new 30- and 45-day windows. And when Anthropic and a maintainer disagree on severity, the policy says Anthropic generally defers to the maintainer, unless there is credible evidence of active exploitation, in which case the 7-day target applies.

There is also a catch-up step for old reports. Some high- and critical-severity bugs that Anthropic reported more than 90 days ago are already past the current deadline and still not public. Anthropic says it is telling those maintainers they get an additional 30 days, after which the reports will be published on its disclosure dashboard in line with the updated policy starting January 1, 2027.

Anthropic and Project Zero side by side

  • Clock: Anthropic sets the window by severity. Project Zero's new Full X policy discloses a vulnerability X days after it is reported to the vendor, and says severity is not an effective metric for disclosure decisions.
  • Schedule: Anthropic goes to 30 and 45 days for reports from January 1, 2027. Project Zero is at Full 90 from November 13, 2026, moves to Full 60 on February 2, 2027, and to Full 30 on January 3, 2028.
  • Patch soak time: Anthropic keeps a 30-day gap between a patch and full technical details. Project Zero dropped its extra 30 days of soak time and will no longer use fix status to decide when it discloses, though it will still track fixes.
  • Exceptions: Anthropic keeps 7 days for active exploitation. Project Zero removed its grace period and variant policy; it handles in-the-wild bugs under Google's application security disclosure policy, may publish details already made public by others, discloses on vendor request, and says it will still grant rare exceptions, as it did for Spectre and Meltdown.
  • Why Project Zero is stepping down slowly: it asked the vendors it reports to most, and they worried that an immediate change could expose unfixed bugs while they improve their processes, and could push them to fix new reports before more severe older ones.

Worked example, counting the report day as day zero (neither policy spells out the counting rule): a high-severity bug Anthropic reports to you on January 4, 2027 would be due for disclosure on February 3, 2027, and a medium-severity one reported the same day on February 18, 2027. Project Zero's post gives its switch dates but does not say whether reports already open on February 2, 2027 keep 90 days or move to 60.

Why the numbers make this hard for maintainers

Anthropic's CVD dashboard, last updated November 2, 2026, shows the scale. Claude models, including an early snapshot of Claude Mythos Preview, produced 37,966 candidate findings. External security firms reviewed 6,376 and confirmed 6,009 as valid, a 94.2% true-positive rate; Anthropic notes that this rate also counts real bugs that turned out to be already reported or that maintainers won't fix. Anthropic has reported 5,087 vulnerabilities across 680 open-source projects: 1,862 after firm triage and 3,225 sent directly to maintainers without the same independent check, which the dashboard says may contain false positives. Maintainers have acknowledged 3,635, 629 have been patched upstream, and 230 CVE records and 503 GitHub Security Advisories have been issued.

By our arithmetic, about 12% of reported vulnerabilities had an upstream patch on that date, and about 71% had been acknowledged. Anthropic says patches are a lagging indicator, since fixes take time to create. Project Zero describes the same pressure from its side: it now finds several vulnerabilities a week in targets where it once found a few a year.

What to do if you maintain an open-source project

  • Answer the first report fast. Under the new policy, Anthropic aims to bring in an outside coordinator if it hears nothing for 15 days.
  • Triage by severity. For a high or critical report sent on or after January 1, 2027, the disclosure window is 30 days, not 90; full technical details follow 30 days after a patch is available.
  • Ask about pace before a batch arrives. Anthropic says it agrees on a sustainable pace with a maintainer before sending a large volume of findings to one project, and includes actionable guidance and, where possible, a patch or mitigation with each report.
  • Raise hard cases early. In our view, if a fix needs a spec change or a slow rollout, it is better to say so to the reporter as soon as you know, since that is the case Anthropic says it will negotiate.
  • Know what the programs are. OSS Scanner is a no-cost service for maintainers of critical open-source projects that scans their code with Anthropic's strongest models; its reports are fully model-generated without human review, and in Anthropic's validation of 97 critical and high findings across 48 projects, 85 met its CVD bar, 11 were real but duplicates, and one was invalid. Anthropic's November 16 post also points eligible maintainers and contributors to the Claude for Open Source Program, which it describes as six months of Claude Ultra at no cost, and security professionals to the Cyber Verification Program.

Try it with your AI. Paste this into your coding agent to check whether your repository's security policy is ready for shorter disclosure deadlines. Fill in the brackets first; it only reads files and drafts changes for you to review.

I maintain the open-source project in this repository. Some security researchers are
moving to shorter disclosure deadlines. For example, for reports sent from January 1,
2027, Anthropic will disclose high- and critical-severity bugs 30 days after reporting
them (45 days for other severities) and aims to escalate to an outside coordinator if a
maintainer has not responded after 15 days.

First, check whether the repository has a security policy file (for example SECURITY.md
or .github/SECURITY.md) and summarize what it says now: how to report a vulnerability,
who receives reports, how quickly we respond, how we handle severity disagreements and
embargoes.

Then draft an updated security policy that keeps every existing private reporting
channel and process unless I tell you otherwise, and adds:
1. One private reporting channel: [our private security contact or GitHub private
   vulnerability reporting]. Do not invent a contact.
2. An acknowledgement target of [number] days. Note that this is our own target, not a
   requirement from any researcher.
3. How we triage by severity, with high and critical issues fixed first.
4. The supported versions that receive security fixes: [versions]. Do not guess
   versions.

Show me the current file and your draft side by side and wait for my confirmation. Do
not commit, push, delete files, or change repository settings.

FAQ

When does Anthropic's 30-day disclosure window start? It applies to vulnerabilities reported to vendors and maintainers on or after January 1, 2027. Reports already in progress on that date keep their existing deadlines, so the first disclosures under the new window come about a month later.

Does the 30-day window apply to every bug? No. It covers high- and critical-severity issues. Other severities get 45 days, actively exploited bugs keep the 7-day target, and unreviewed findings from OSS Scanner are not covered.

What happens if a maintainer does not respond to Anthropic's first report? Anthropic will aim to escalate to an external vulnerability coordinator after 15 days instead of 30.

Is Project Zero also at 30 days? Not yet. Project Zero is on Full 90 from November 13, 2026, moves to Full 60 on February 2, 2027, and reaches Full 30 on January 3, 2028.

Source: Anthropic: Updating our coordinated vulnerability disclosure policy timelines, Anthropic coordinated vulnerability disclosure policy, Anthropic coordinated vulnerability disclosure dashboard, Google Project Zero: Policy and Disclosure: 2026 Edition, Anthropic: OSS Scanner for open-source maintainers

This story first appeared in the claudefox daily briefing for November 17, 2026.