CVE-2026-45752 OISF CVE debrief

Who should care

Defenders responsible for network security, intrusion detection, and intrusion prevention systems should be aware of this vulnerability and take steps to address it. This includes updating Suricata to version 8.0.5 or later, reviewing and restricting the use of malicious rules, and monitoring Suricata logs for potential crashes. Additionally, defenders should review compensating controls for exposed systems while remediation is scheduled and verified, and

Why it matters

Defenders should prioritize updating Suricata to version 8.0.5 or later to address this vulnerability. The issue arises when certain detection transforms are chained, allowing the decompress transform pipeline to read from an inspection buffer after it has been reallocated and freed. This can be triggered by a malicious rule, causing Suricata to crash regardless of the network traffic.

• Denial-of-service condition due to Suricata crashes
• Potential for malicious rules to trigger the vulnerability
• Need for updated Suricata version or workarounds to prevent crashes

Technical summary

The vulnerability arises when certain detection transforms are chained, allowing the decompress transform pipeline to read from an inspection buffer after it has been reallocated and freed. This can be triggered by a malicious rule, causing Suricata to crash regardless of the network traffic. The issue is addressed in Suricata version 8.0.5. A workaround is to avoid rules that chain `gunzip` or `zlib_deflate` with `max-size` bigger than 4096 after another transform. Defenders should prioritize updating Suricata to version 8.0.5 or later to address this vulnerability.

Defensive priority

Defenders should prioritize updating Suricata to version 8.0.5 or later to address this vulnerability. Additionally, they should review and restrict the use of malicious rules that could trigger this issue.

Recommended defensive actions

• Update Suricata to version 8.0.5 or later
• Review and restrict the use of malicious rules
• Monitor Suricata logs for potential crashes
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE record and NVD vulnerability detail page. The issue is addressed in Suricata version 8.0.5. A workaround is to avoid rules that chain `gunzip` or `zlib_deflate` with `max-size` bigger than 4096 after another transform.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.