Claude (Anthropic) Claude Sonnet 5.5 · Version Status

Claude (Anthropic) Claude Sonnet 5.5 End of Life Date

Claude (Anthropic) Claude Sonnet 5.5 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

✓ Claude (Anthropic) Claude Sonnet 5.5 is actively supported. EOL date: September 28, 2027.
📅 Get reminded before Claude (Anthropic) Claude Sonnet 5.5 reaches EOL on September 28, 2027 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Sep 28, 2027
363 days remaining
Latest Release
—
Standard release
Release Date
Sep 28, 2026
Claude (Anthropic) Claude Sonnet 5.5 series
Lifecycle detail

Claude (Anthropic) claude-sonnet-5-5 was released on September 28, 2026 and support is scheduled to end on September 28, 2027 — a planned supported lifespan of 1 year, shorter than the 1 year and 7 months median for Claude (Anthropic) releases.

← Claude (Anthropic) Claude Opus 5.5 All Claude (Anthropic) versions
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
20/30 High tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Claude (Anthropic) Versions
VersionLatestEOL DateStatus
Claude 1.0 — Nov 6, 2024 EOL
Claude Instant 1.0 — Nov 6, 2024 EOL
Claude 1.1 — Nov 6, 2024 EOL
Claude 1.2 — Nov 6, 2024 EOL
Claude Instant 1.1 — Nov 6, 2024 EOL
Claude 1.3 — Nov 6, 2024 EOL
Claude 2.0 — Jul 21, 2025 EOL
Claude Instant 1.2 — Nov 6, 2024 EOL

What does Claude (Anthropic) Claude Sonnet 5.5 end of life mean?

When Claude (Anthropic) Claude Sonnet 5.5 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Claude (Anthropic) Claude Sonnet 5.5 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Claude (Anthropic) Claude Sonnet 5.5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Claude (Anthropic) Claude Sonnet 5.5 reach end of life?
Claude (Anthropic) Claude Sonnet 5.5 reached end of life on September 28, 2027. That is 363 days remaining.
Is Claude (Anthropic) Claude Sonnet 5.5 still supported?
Yes, Claude (Anthropic) Claude Sonnet 5.5 is currently supported. The EOL date is September 28, 2027.
What should I upgrade to from Claude (Anthropic) Claude Sonnet 5.5?
The recommended upgrade from Claude (Anthropic) Claude Sonnet 5.5 is Claude (Anthropic) Claude Sonnet 5.5 — the latest actively supported version. Check the Claude (Anthropic) full timeline for all supported versions.
What are the security risks of running Claude (Anthropic) Claude Sonnet 5.5 past EOL?
When Claude (Anthropic) Claude Sonnet 5.5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Claude (Anthropic) should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →