Monitoring interruption via unbounded NFS parser state
Published Sep 10, 2026 · Updated Sep 10, 2026
Memory exhaustion in Suricata's NFS parser before 7.0.16 and 8.0.0 through 8.0.4 allows remote attackers to interrupt monitoring via crafted traffic. The parser maintains NFS state in structures without sufficient bounds, so attacker-controlled traffic can drive excessive memory consumption. NFS application-layer parsing must receive the traffic; exhaustion can stop Suricata monitoring, with no reported confidentiality or integrity impact.
Summary
What happened
Memory exhaustion in Suricata's NFS parser before 7.0.16 and 8.0.0 through 8.0.4 allows remote attackers to interrupt monitoring via crafted traffic. The parser maintains NFS state in structures without sufficient bounds, so attacker-controlled traffic can drive excessive memory consumption. NFS application-layer parsing must receive the traffic; exhaustion can stop Suricata monitoring, with no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2026-45766
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Open Information Security Foundation
- Product
- Suricata
- Classifications
- CWE-400, CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.0.16
- Affected versionversion=>= 8.0.0, < 8.0.5
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