Ros 2 kilted · Version Status

Ros 2 kilted End of Life Date

Ros 2 kilted end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Ros 2 kilted is actively supported. EOL date: December 31, 2026.
EOL Date
Dec 31, 2026
236 days remaining
Latest Release
Standard release
Release Date
May 23, 2025
Ros 2 kilted series
← Ros 2 jazzy All Ros 2 versions
All Ros 2 Versions
VersionLatestEOL DateStatus
ardent Dec 31, 2018 EOL
bouncy Jul 31, 2019 EOL
crystal Dec 31, 2019 EOL
dashing May 31, 2021 EOL
eloquent Nov 30, 2020 EOL
foxy Jun 20, 2023 EOL
galactic Dec 9, 2022 EOL
humble May 31, 2027 Active

What does Ros 2 kilted end of life mean?

When Ros 2 kilted 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 Ros 2 kilted past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Ros 2 kilted or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Ros 2 kilted reach end of life?
Ros 2 kilted reached end of life on December 31, 2026. That is 236 days remaining.
Is Ros 2 kilted still supported?
Yes, Ros 2 kilted is currently supported. The EOL date is December 31, 2026.
What should I upgrade to from Ros 2 kilted?
The recommended upgrade from Ros 2 kilted is Ros 2 kilted — the latest actively supported version. Check the Ros 2 full timeline for all supported versions.
What are the security risks of running Ros 2 kilted past EOL?
When Ros 2 kilted 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 Ros 2 should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →