Skip to main content
VulnerabilityPublished Updated

CVE-2024-47522: OISF suricata · Reachable Assertion

Affects OISF suricataSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High : upgrade to 7.0.7 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.0.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Oct 2024

  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 7.0.7.

Affected software

ProductAffectedFixed in
GitHuboisf/suricatapkg:github/oisf/suricataOther threatsAffected
  • <7.0.7
Fixed in
  • 7.0.7

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

AI-suggested

Upgrade Suricata to version 7.0.7 or later, where this vulnerability is fixed. As a temporary workaround, disable JA4 matching and logging to prevent the panic.

Description

CVE-2024-47522 is a high-severity vulnerability in Suricata versions prior to 7.0.7. It involves a reachable assertion triggered by invalid ALPN values in TLS/QUIC traffic when JA4 matching and logging is enabled, causing Suricata to abort with a panic. This can lead to a denial of service condition. The issue is addressed in Suricata version 7.0.7. As a temporary mitigation, disabling JA4 matching can prevent the panic. There are no known exploits in the wild at this time.

References

Community reviews

Loading reviews…