Calico 3.31 · Version Status

Calico 3.31 End of Life Date

Calico 3.31 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Calico 3.31 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
3.31.5
Standard release
Release Date
Oct 21, 2025
Calico 3.31 series
← Calico 3.30 All Calico versions
All Calico Versions
VersionLatestEOL DateStatus
3.25 3.25.2 Dec 15, 2023 EOL
3.26 3.26.5 May 11, 2024 EOL
3.27 3.27.5 Oct 29, 2024 EOL
3.28 3.28.5 May 5, 2025 EOL
3.29 3.29.7 Oct 21, 2025 EOL
3.30 3.30.7 EOL Active
3.31 3.31.5 EOL Active

What does Calico 3.31 end of life mean?

When Calico 3.31 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Calico 3.31 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Calico 3.31 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Calico 3.31 reach end of life?
Calico 3.31 has already reached end of life.
Is Calico 3.31 still supported?
Yes, Calico 3.31 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Calico 3.31?
The recommended upgrade from Calico 3.31 is Calico 3.31 — the latest actively supported version. Check the Calico full timeline for all supported versions.
What are the security risks of running Calico 3.31 past EOL?
When Calico 3.31 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Calico should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →