Local heap over-read via trailing LDIF semicolon
Published Jun 9, 2026 · Updated Jun 9, 2026
Out-of-bounds read in the LDIF parser in 389 Directory Server allows local users to over-read heap memory during database import. In str2entry_state_information_from_type(), a semicolon found by PL_strchr leads to reads of p[3] through p[6] without checking the allocation's remaining length. Exploitation requires local administrator access to run ldif2db; ASan detects the read, while allocator padding prevents crashes in production binaries.
Summary
What happened
Out-of-bounds read in the LDIF parser in 389 Directory Server allows local users to over-read heap memory during database import. In str2entry_state_information_from_type(), a semicolon found by PL_strchr leads to reads of p[3] through p[6] without checking the allocation's remaining length. Exploitation requires local administrator access to run ldif2db; ASan detects the read, while allocator padding prevents crashes in production binaries.
The record
- CVE
- CVE-2026-11786
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Directory Server
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo