Skip to content
Fencer Intel
medium 5.3

CVE-2026-22263 json

Suricata http1: quadratic complexity in headers parsing over multiple packets

published 9mo ago modified 4mo ago also EUVD-2026-4771

cvss
5.3
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 38%
public exploits
0
none known

Summary

Suricata is a network IDS, IPS and NSM engine. Starting in version 8.0.0 and prior to version 8.0.3, inefficiency in http1 headers parsing can lead to slowdown over multiple packets. Version 8.0.3 patches the issue. No known workarounds are available.

Patch / fix

  • oisf suricata 8.0.3
  • suricata Debian 14 1:8.0.3-1

debian advisories DEBIAN-CVE-2026-22263

  • suricata openSUSE Tumbleweed 8.0.3-1.1

opensuse advisories openSUSE-SU-2026:10082-1

Is CVE-2026-22263 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-22263 updated cvss 5.3

suricata: Suricata: Denial of Service via inefficient HTTP/1 header parsing

  • 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
yes
Technical impact
partial
Assessed
9mo ago

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 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 Intel 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.