Skip to main content
VulnerabilityPublished

CVE-2026-45751: OISF suricata · Use After Free

Affects OISF suricataSource GCVE Database

0

Not known to be exploited · CVSS 5.9 Medium : upgrade to 8.0.5 or 7.0.16 when convenient.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.5, 7.0.16
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade oisf/suricata to 8.0.5 or 7.0.16.

Affected software

ProductAffectedFixed in
GitHuboisf/suricatapkg:github/oisf/suricataOther threatsAffected
  • <7.0.16
  • >=8.0.0 <8.0.5
Fixed in
  • 7.0.16
  • 8.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Suricata versions 7.0.16 and 8.0.5. Users should upgrade to these versions or later. As a temporary workaround, avoid using rules that chain the 'dotprefix' transform after another transform. No other mitigation actions are indicated.

Description

CVE-2026-45751 is a use-after-free vulnerability in Suricata's inspection-buffer helper that affects versions prior to 7.0.16 and between 8.0.0 and 8.0.5. The issue occurs when a chained transform causes the backing buffer to be reallocated, leaving an inspection pointer referencing freed memory. This vulnerability requires a specific network traffic processing scenario and a particular but non-malicious rule involving the 'dotprefix' transform. Versions 7.0.16 and 8.0.5 include a fix for this issue. A workaround is to avoid chaining the 'dotprefix' transform after another transform.

References

Community reviews

Loading reviews…