Ros 2 galactic · Version Status
Ros 2 galactic End of Life Date
Ros 2 galactic end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Ros 2 galactic is past end of life. This version no longer receives security patches. 1247 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 9, 2022
1247 days past EOL
Latest Release
—
Standard release
Release Date
May 23, 2021
Ros 2 galactic series
What does Ros 2 galactic end of life mean?
When Ros 2 galactic 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 galactic 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 galactic reach end of life?
Ros 2 galactic reached end of life on December 9, 2022. This version is no longer receiving security patches.
Is Ros 2 galactic still supported?
No. Ros 2 galactic reached end of life on December 9, 2022 and is no longer receiving security patches.
What should I upgrade to from Ros 2 galactic?
The recommended upgrade from Ros 2 galactic 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 galactic past EOL?
When Ros 2 galactic 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.