CVE-2026-18355
What it is
A heap buffer overflow flaw was found in the SASL I/O layer of 389 Directory Server (389-ds-base). In sasl_io_start_packet(), the wrapped-record length read from the wire is validated only against an upper bound. A small wire length (0, 1, or 2) produces an encrypted_buffer_count below the already-consumed encrypted_buffer_offset, causing an unsigned subtraction underflow in sasl_io_read_packet(). PR_Recv is then requested to read approximately 4 GiB into a 1024-byte heap buffer, resulting in a heap buffer overflow with attacker-controlled content. After a successful SASL bind with integrity protection (SSF > 0), a remote authenticated attacker can cause a denial of service or potentially achieve remote code execution. This flaw is distinct from CVE-2026-11774, whose fix only guards against upper-bound overflow.
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.8% · EPSS, next 30 days
- Weakness
- CWE-191
- Record status
- Awaiting Analysis
Attack profile CVSS 3.1 · 7.5
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-18355.md and follow it. Check whether this project is affected by CVE-2026-18355. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://access.redhat.com/errata/RHSA-2026:64771
- https://access.redhat.com/errata/RHSA-2026:64776
- https://access.redhat.com/errata/RHSA-2026:64778
- https://access.redhat.com/errata/RHSA-2026:64779
- https://access.redhat.com/errata/RHSA-2026:64780
- https://access.redhat.com/errata/RHSA-2026:64781
- https://access.redhat.com/errata/RHSA-2026:64783
- https://access.redhat.com/errata/RHSA-2026:64784
- https://access.redhat.com/errata/RHSA-2026:64785
- https://access.redhat.com/errata/RHSA-2026:64789
- https://access.redhat.com/errata/RHSA-2026:64790
- https://access.redhat.com/errata/RHSA-2026:64791
- https://access.redhat.com/errata/RHSA-2026:64792
- https://access.redhat.com/errata/RHSA-2026:64793
- https://access.redhat.com/errata/RHSA-2026:64804
- https://access.redhat.com/errata/RHSA-2026:65119
- https://access.redhat.com/errata/RHSA-2026:79217
- https://access.redhat.com/security/cve/CVE-2026-18355
- https://bugzilla.redhat.com/show_bug.cgi?id=2509186