Sles 12.3 · Version Status

Sles 12.3 End of Life Date

Sles 12.3 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Sles 12.3 is past end of life. This version no longer receives security patches. 2505 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 30, 2019
2505 days past EOL
Latest Release
Standard release
Release Date
Sep 7, 2017
Sles 12.3 series
← Sles 12.2 All Sles versions Sles 15.0 →
Recommended upgrade path
Sles 16.0
Latest release: — · EOL: Nov 30, 2027
View full Sles timeline →
All Sles Versions
VersionLatestEOL DateStatus
10.0 Dec 31, 2007 EOL
10.1 Nov 30, 2008 EOL
10.2 Apr 11, 2010 EOL
11.0 Dec 31, 2010 EOL
10.3 Oct 11, 2011 EOL
11.1 Aug 31, 2012 EOL
10.4 Jul 31, 2013 EOL
11.2 Jan 31, 2014 EOL

What does Sles 12.3 end of life mean?

When Sles 12.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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Sles 12.3 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Sles 16.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Sles 12.3 reach end of life?
Sles 12.3 reached end of life on June 30, 2019. This version is no longer receiving security patches.
Is Sles 12.3 still supported?
No. Sles 12.3 reached end of life on June 30, 2019 and is no longer receiving security patches.
What should I upgrade to from Sles 12.3?
The recommended upgrade from Sles 12.3 is Sles 16.0 — the latest actively supported version. Check the Sles full timeline for all supported versions.
What are the security risks of running Sles 12.3 past EOL?
When Sles 12.3 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 Sles should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →