CVE-2026-45768
largeUnbounded memory growth in Suricata LDAP parsing enables remote DoS
Suricata versions 8.0.0 through before 8.0.5 can store an unbounded number of responses in LDAP transaction state, so crafted LDAP traffic, which can be delivered over UDP, drives excessive memory consumption in the engine and can cause a denial of service. A remote, unauthenticated attacker who can send traffic across a monitored link can trigger the condition; the impact is limited to sensor availability, with no confidentiality or integrity impact (CVSS 3.1: 7.5 High, availability only; CWE-400/CWE-770 uncontrolled resource consumption). Only deployments running Suricata 8.0.0 or later are affected, with the flaw fixed in 8.0.5, and sensors that do not inspect LDAP application-layer traffic are largely unaffected in practice. No public proof of concept or in-the-wild exploitation is known, and the issue is not in CISA's Known Exploited Vulnerabilities catalog. Defenders running the affected range should upgrade to 8.0.5 or apply the documented workarounds.
What to do: Upgrade Suricata to version 8.0.5. Where upgrading is not immediately possible, disable LDAP application-layer parsing on sensors that do not need it, or add a bypass rule that bypasses LDAP transactions carrying more than 1024 responses. Check whether monitored links carry LDAP traffic, particularly LDAP over UDP, since exposure requires that traffic.
| OISF Suricata | 8.0.0 and later, prior to 8.0.5 (fixed in 8.0.5) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Starting in version 8.0.0 and prior to version 8.0.5, LDAP transaction state could store an unbounded number of responses. Because LDAP can be processed over UDP, crafted traffic may cause Suricata to consume excessive memory, potentially resulting in denial of service. Version 8.0.5 contains a fix. As a workaround, disable LDAP application-layer parsing where it is not required. Alternatively, use a rule like `alert ldap any any -> any any (sid: 1; ldap.responses.count: >1024; bypass;)`.
- Weakness
- CWE-400, CWE-770
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
In the news0 stories
No ingested article mentions this CVE yet.