Security
Anthropic cuts its disclosure window for high and critical vulnerabilities from 90 to 30 days, starting January 2027
Anthropic’s November 16 policy update cuts disclosure to 30 days for high and critical bugs and 45 for the rest, for reports from January 1, 2027.
Anthropic announced on November 16 that it is shortening its coordinated vulnerability disclosure window from 90 days to 30 days for high- and critical-severity bugs, and to 45 days for everything else. The change applies to vulnerabilities reported from January 1, 2027, not immediately. Anthropic says AI makes the same flaws easier to rediscover, so the old timetable is harder to justify.
The essentials
- The change: 30 days for high and critical issues, down from 90, and 45 days for others.
- When: it applies to reports made on or after January 1, 2027.
- Other timings: Anthropic will reportedly seek an outside coordinator after 15 days without a maintainer response, down from 30, and publish full details 30 days after a patch instead of 45.
- The reason: AI-assisted discovery means others may find the same bug before the deadline.
What stays the same
One summary lists actively exploited vulnerabilities at 7 days, unchanged. Anthropic’s policy concerns bugs its models find and report, not every vendor’s disclosure practice.
The trade-off
Maintainers get a third of the time to fix serious bugs, which is hard for small projects. Anthropic’s argument is that a long delay is riskier when other AI systems can find the same flaw. We did not read the policy page itself.
What is not established
- The text of Anthropic’s policy page: not read directly.
- How maintainers will be helped to fix bugs faster: not established.
- Whether other vendors will follow: not stated.
- How many open bugs are past 90 days: only described as “some”.
- Effects on small open-source projects: not measured.
Summary table
| Point | What is stated as of November 17, 2026 | Source |
|---|---|---|
| High and critical severity | 30 days (was 90) | ShiftDelete.Net |
| Other issues | 45 days | FourWeekMBA |
| Effective for reports from | January 1, 2027 | Blockchain.News |
| Outside coordinator | After 15 days without a response (was 30) | Techbooky |
| After a patch | 30 days before full details (was 45) | Techbooky |
FAQ
Does the 30-day rule apply now?
No. It applies to vulnerabilities reported from January 1, 2027.
Does it cover every vulnerability?
It covers bugs reported under Anthropic’s coordinated disclosure policy, with 30 days for high and critical and 45 for others.
Why shorten it?
Anthropic says AI speeds up discovery, making it likelier that others find the same flaw before a long deadline ends.
Method and limits
Checked on November 17, 2026. We read FourWeekMBA, ShiftDelete.Net, Techbooky and Blockchain.News through search excerpts. We did not read Anthropic’s policy page directly.
Sources
- FourWeekMBA: Anthropic Cuts Bug Disclosure Window to 30 Days From 90 (verified 2026-11-17)
- ShiftDelete.Net: Anthropic Cuts Vulnerability Disclosure Window From 90 to 30 Days (verified 2026-11-17)
- Techbooky: Anthropic Cuts AI-Found Vulnerability Disclosure Window to 30 Days (verified 2026-11-17)
- Blockchain.News: Anthropic Shortens Vulnerability Disclosure Timelines Amid AI Advances (verified 2026-11-17)
Spotted an error in this article? Report it · Our corrections policy