Skip to content
Fencer Vulns
low 3.7

CVE-2026-22261 json

Suricata eve/alert: http1 xff handling can lead to denial of service

published 2026-01-27 9 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-4786

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

Suricata is a network IDS, IPS and NSM engine. Prior to versions 8.0.3 and 7.0.14, various inefficiencies in xff handling, especially for alerts not triggered in a tx, can lead to severe slowdowns. Versions 8.0.3 and 7.0.14 contain a patch. As a workaround, disable XFF support in the eve configuration. The setting is disabled by default.

Patch / fix

  • oisf suricata 7.0.14, 8.0.3
  • suricata Debian 13 1:7.0.10-1+deb13u3
  • suricata Debian 14 1:8.0.3-1

debian advisories DEBIAN-CVE-2026-22261

  • suricata openSUSE Tumbleweed 8.0.3-1.1

opensuse advisories openSUSE-SU-2026:10082-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-22261 updated cvss 3.7

suricata: Suricata: Denial of Service due to XFF handling inefficiencies

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected products

  • OISF suricata

Classification

Weakness
  • CWE-1050 Excessive Platform Resource Consumption within a Loop

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.