OpenSAML 3 · Version Status
OpenSAML 3 End of Life Date
OpenSAML 3 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (shibboleth.atlassian.net); the source of each date is on the product page.
⚠
OpenSAML 3 is past end of life. This version no longer receives security patches. 2136 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 31, 2020
2136 days past EOL
Latest Release
3.4.6
Standard release
Release Date
—
OpenSAML 3 series
Where these dates come from
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
It has been past its end-of-life date for 5 years and 10 months.
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 OpenSAML 3 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 →
| Version | Latest | EOL Date | Status |
|---|
| → 3 |
3.4.6 |
Dec 31, 2020 |
EOL |
| 4 |
4.3.2 |
Sep 1, 2024 |
EOL |
| 5 |
5.2.3 |
EOL |
Active |
What does OpenSAML 3 end of life mean?
When OpenSAML 3 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 OpenSAML 3 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to OpenSAML 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does OpenSAML 3 reach end of life?
OpenSAML 3 reached end of life on December 31, 2020. This version is no longer receiving security patches.
Is OpenSAML 3 still supported?
No. OpenSAML 3 reached end of life on December 31, 2020 and is no longer receiving security patches.
What should I upgrade to from OpenSAML 3?
The recommended upgrade from OpenSAML 3 is
OpenSAML 5 — the latest actively supported version. Check the
OpenSAML full timeline for all supported versions.
What are the security risks of running OpenSAML 3 past EOL?
Since OpenSAML 3 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 OpenSAML should migrate immediately or implement compensating controls.