Skip to content
VulniPulse
Advisory severityCritical9.0Vendor: MediumRed Hat Linux

Critical [CVE-2026-86345] StartTLS plaintext-buffer retention allows on-path attacker to forge an LDAP client's authentication result

This critical-severity Red Hat Linux advisory covers CVE-2026-86345; related products: Red Hat Directory Server 11, Red Hat Directory Server 12, Red Hat Directory Server 13.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-86345 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

StartTLS plaintext-buffer retention allows on-path attacker to forge an LDAP client's authentication result. Red Hat rates this moderate (CVSS 9).

Weakness: CWE-923.

Affected products named by the advisory: Red Hat Directory Server 11; Red Hat Directory Server 12; Red Hat Directory Server 13; Red Hat Enterprise Linux 10; and 2 more.

Affected products named by the advisory: Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Mitigation checklist

Temporary workarounds
  • 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.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.