cve.bz

CVE-2026-86345

9.0 criticalEPSS 0.4%

Critical (9.0). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in 389-ds-base. The server does not discard plaintext bytes already buffered from a client connection when negotiating StartTLS, allowing an on-path attacker to inject a crafted LDAP message that is processed after the TLS upgrade and whose response is delivered to the client in place of the client's own pending operation's response, due to messageID collision. This can cause a client application to treat a failed authentication (bind) attempt as successful.

Severity

CVSS 3.1

9.0 critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-923 Improper Restriction of Communication Channel to Intended Endpoints
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-86345 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86345?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86345?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86345 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13389-ds-baseno fix listedDEBIAN-CVE-2026-86345
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 more389-ds-baseno fix listedUBUNTU-CVE-2026-86345
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Server 15 SP5-LTSS and 1 more389-ds2.2.11~git12.1e612cde2-150500.3.54.1SUSE-SU-2026:4932-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6389-ds2.2.11~git12.1e612cde2-150600.8.38.1SUSE-SU-2026:4929-1
openSUSETumbleweed389-ds3.3.1+28b6d8afc-1.1openSUSE-SU-2026:12312-1
Azure Linux3389-ds-baseno fix listedAZL-107954

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated Moderate rather than Critical or Important, despite a CVSS base score of 9.0. Exploitation requires an attacker to hold an active on-path (man-in-the-middle) position on the network segment between an LDAP client and the server at the moment StartTLS is negotiated -- a materially harder precondition than a purely remote, unauthenticated attack, and one that rules out the ease-of-exploitation bar Critical requires. The outcome is also not arbitrary code execution: exploitation causes a client-side application (e.g. a PAM module) to incorrectly treat a failed authentication attempt as successful, granting access through that application's own, legitimate, pre-existing login mechanism rather than through execution of attacker-supplied code. 389-ds-base itself is not compromised by this flaw -- the server suffers no privilege escalation and no data exfiltration beyond what an anonymous bind could already obtain; the security impact is entirely realized in separate, downstream client applications that trust the LDAP bind result.

Red Hat's mitigation

Disable StartTLS on port 389 and require ldaps:// (port 636) instead, which has no cleartext prefix to inject into. No configuration-only mitigation fully closes the issue on port 389 while StartTLS remains enabled.

ProductPackageStateAdvisory
Red Hat Directory Server 11389-ds-baseAffected
Red Hat Directory Server 11redhat-ds:11/389-ds-baseAffected
Red Hat Directory Server 12389-ds-baseAffected
Red Hat Directory Server 12redhat-ds:12/389-ds-baseAffected
Red Hat Directory Server 13389-ds-baseAffected
Red Hat Enterprise Linux 10389-ds-baseAffected
Red Hat Enterprise Linux 6389-ds-baseOut of support scope
Red Hat Enterprise Linux 7389-ds-baseOut of support scope
Red Hat Enterprise Linux 8389-ds:1.4/389-ds-baseAffected
Red Hat Enterprise Linux 8389-ds-baseAffected
Red Hat Enterprise Linux 9389-ds-baseAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-86345.

Attack patterns (CAPEC)

  • CAPEC-161 Infrastructure Manipulation Severity: High
  • CAPEC-481 Contradictory Destinations in Traffic Routing Schemes Likelihood: Medium · Severity: High
  • CAPEC-501 Android Activity Hijack Severity: Medium
  • CAPEC-697 DHCP Spoofing Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON