Tls 1.1 · Version Status
Tls 1.1 End of Life Date
Tls 1.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Tls 1.1 is past end of life. This version no longer receives security patches. 1873 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 23, 2021
1873 days past EOL
Latest Release
—
Standard release
Release Date
Apr 26, 2006
Tls 1.1 series
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
— |
Mar 23, 2021 |
EOL |
| → 1.1 |
— |
Mar 23, 2021 |
EOL |
| 1.2 |
— |
EOL |
Active |
| 1.3 |
— |
EOL |
Active |
What does Tls 1.1 end of life mean?
When Tls 1.1 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 Tls 1.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Tls 1.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Tls 1.1 reach end of life?
Tls 1.1 reached end of life on March 23, 2021. This version is no longer receiving security patches.
Is Tls 1.1 still supported?
No. Tls 1.1 reached end of life on March 23, 2021 and is no longer receiving security patches.
What should I upgrade to from Tls 1.1?
The recommended upgrade from Tls 1.1 is
Tls 1.3 — the latest actively supported version. Check the
Tls full timeline for all supported versions.
What are the security risks of running Tls 1.1 past EOL?
When Tls 1.1 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 Tls should migrate immediately or implement compensating controls.