ROS 2 eloquent · Version Status
ROS 2 eloquent End of Life Date
ROS 2 eloquent 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.
⚠
ROS 2 eloquent is past end of life. This version no longer receives security patches. 2168 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 30, 2020
2168 days past EOL
Latest Release
—
Standard release
Release Date
Nov 22, 2019
ROS 2 eloquent series
Where these dates come from
End of lifeNov 30, 2020endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseNov 22, 2019endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
ROS 2 eloquent was released on November 22, 2019 and support ended on November 30, 2020 — a supported lifespan of 1 year, shorter than the 1 year and 7 months median for ROS 2 releases. It has been past its end-of-life date for 5 years and 11 months. 6 newer ROS 2 releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 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 →
Extended Support
Extended ROS 2 eloquent support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
What does ROS 2 eloquent end of life mean?
When ROS 2 eloquent 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 ROS 2 eloquent past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to ROS 2 lyrical or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does ROS 2 eloquent reach end of life?
ROS 2 eloquent reached end of life on November 30, 2020. This version is no longer receiving security patches.
Is ROS 2 eloquent still supported?
No. ROS 2 eloquent reached end of life on November 30, 2020 and is no longer receiving security patches.
What should I upgrade to from ROS 2 eloquent?
The recommended upgrade from ROS 2 eloquent is
ROS 2 lyrical — the latest actively supported version. Check the
ROS 2 full timeline for all supported versions.
What are the security risks of running ROS 2 eloquent past EOL?
Since ROS 2 eloquent reached end of life, the maintainers no longer issue 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 ROS 2 should migrate immediately or implement compensating controls.