OpenLDAP 2.7 · Version Status

OpenLDAP 2.7 End of Life Date

OpenLDAP 2.7 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (openldap.org); the source of each date is on the product page.

✓ OpenLDAP 2.7 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
2.7.1
Standard release
Release Date
Aug 6, 2026
OpenLDAP 2.7 series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

OpenLDAP 2.7 was released on August 6, 2026 and has no published end-of-life date yet. It is not an LTS release; OpenLDAP reserves longer patch windows for its LTS versions. Its most recent patch is 2.7.1, published September 8, 2026.

← OpenLDAP 2.6 All OpenLDAP versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 →
All OpenLDAP Versions
VersionLatestEOL DateStatus
2.4 2.4.59 Oct 25, 2021 EOL
2.5 2.5.20 Jan 15, 2027 Warning
2.6 LTS 2.6.15 EOL Active
→ 2.7 2.7.1 EOL Active

What does OpenLDAP 2.7 end of life mean?

When OpenLDAP 2.7 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 OpenLDAP 2.7 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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

Frequently Asked Questions
When does OpenLDAP 2.7 reach end of life?
OpenLDAP 2.7 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is OpenLDAP 2.7 still supported?
Yes, OpenLDAP 2.7 is currently supported. The EOL date is TBD.
What should I upgrade to from OpenLDAP 2.7?
The recommended upgrade from OpenLDAP 2.7 is OpenLDAP 2.7 — the latest actively supported version. Check the OpenLDAP full timeline for all supported versions.
What are the security risks of running OpenLDAP 2.7 past EOL?
When OpenLDAP 2.7 reaches end of life, the maintainers stop issuing 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 OpenLDAP should migrate immediately or implement compensating controls.
Data from the vendor's own lifecycle pages (openldap.org) · Generated at build time · How we source data →