A third of the time, on a fixed start date
The change is simple to state and harder to absorb. From January 1, 2027, a serious flaw reported by Anthropic's researchers gives the software maker a standard disclosure window of 30 days, not 90. Everything below high severity gets 45 days. Two secondary clocks shrink with it: after 15 days without a response Anthropic will aim to escalate to an external coordinator, rather than 30, and the wait between a patch shipping and full technical details appearing falls from 45 days to 30.
Reports already in progress are not pulled forward. They keep the deadlines they started with. The one exception cuts the other way: Anthropic gives the specified overdue high- and critical-severity reports an additional 30 days, with dashboard publication under the updated policy beginning January 1, 2027.
The argument is rediscovery, not impatience
Anthropic's stated reasoning is worth reading closely, because it is a claim about how bug-finding now works rather than a preference for speed. The old norms, the post says, assumed fixes moved at human speed and that independent rediscovery of the same bug was unlikely. It says neither assumption holds: models can help develop fixes, and a bug one model can find is increasingly likely to be found by another. It reports a higher rate of vulnerability rediscovery as capabilities have increased.
That is the load-bearing claim, and it is presented without numbers. The post gives no rediscovery rate, no count of duplicated findings, and no data on how many vendors currently fix a reported serious flaw inside 30 days. Readers should treat the diagnosis as plausible and the evidence for it as unpublished. The backlog publications may illuminate unresolved cases, but they cannot by themselves establish whether maintainers can remediate newly reported flaws within the new window.
Where the pressure actually lands
Disclosure deadlines do not fall evenly. Maintainers differ in staffing, deployment constraints and remediation capacity. A small open-source project, often maintained by volunteers, now has a third of the previous standard window to confirm a finding, write a fix, test it and ship it, for the class of bugs that matter most. Anthropic says it will agree a sustainable pace with a project before sending it a large volume of findings, and that each report will carry guidance and, where possible, a patch or mitigation. Those commitments will decide whether 30 days reads as urgency or as load.
Two carve-outs limit the headline number. Flaws that cannot be fixed quickly because the software is hard to deploy, critical infrastructure being the example given, and flaws that need a specification or RFC change get an agreed timeline instead of the standard window. And the policy does not cover unreviewed machine output: findings from OSS Scanner that no human has reviewed sit outside these timelines, which keeps the 30-day clock tied to reports a person has actually checked.
Read against Google's slower ramp
Anthropic is not moving alone, and the comparison clarifies the choice it made. Cyber Kendra reports that Google Project Zero announced its own move away from its long-standing 90-plus-30 arrangement on November 13, three days earlier, but on a phased schedule that reaches a 30-day clock later. Anthropic goes straight to 30 days for serious flaws on a single date, January 1, 2027, while keeping a severity split that gives lesser flaws 45. Which design is right depends on more than the unpublished rediscovery question underneath both: remediation capacity and deployment risk matter too. Anthropic's post, at least, publishes no rediscovery figure at all.
Sources
- [1] Anthropic, "Updating our coordinated vulnerability disclosure policy timelines", November 16, 2026 (primary source, read first-hand by ALFW)Read source
- [2] Cyber Kendra, "Anthropic Cuts Vulnerability Disclosure Deadline to 30 Days After Google", November 16, 2026 (Project Zero comparison details)Read source