Security readout for executives and security teams
Plain-English summary
This issue can make Suricata run much slower when X-Forwarded-For handling is enabled in EVE alert output. It affects monitoring capacity, not data confidentiality or integrity. The feature is disabled by default, reducing typical exposure. Organizations using Suricata for IDS, IPS, or NSM should verify configuration and upgrade if running affected versions.
Executive priority
Treat as a routine but time-bound maintenance item. Prioritize internet-facing or high-throughput monitoring points where Suricata availability is operationally important, especially if XFF support was enabled. The business risk is degraded detection performance rather than compromise of protected systems.
Technical view
Suricata before 7.0.14 and 8.0.0 through 8.0.2 has inefficient HTTP/1 XFF processing in EVE alert handling, especially for alerts not triggered in a transaction. A network attacker with high-complexity conditions may cause severe slowdowns. CVSS is 3.7, availability impact low, no privileges or user interaction required.
Likely exposure
Exposure is mainly Suricata deployments below 7.0.14 or 8.0.3 with EVE XFF support enabled. Because XFF support is disabled by default, many default installations may not be affected unless administrators enabled it.
Exploitation context
The provided sources do not indicate active exploitation, and the CVE is not listed as KEV. The CVSS vector rates attack complexity as high and impact as availability-only. Practical risk is higher where Suricata processes untrusted HTTP traffic at high volume with XFF enabled.
Researcher notes
Evidence is limited to the CVE record, OISF advisory, commits, and related issue. The root cause is inefficient XFF handling in EVE alert paths. Avoid assuming broader Suricata components are affected beyond the listed versions and configuration context.
Mitigation direction
- Upgrade Suricata 7.x to 7.0.14 or later.
- Upgrade Suricata 8.x to 8.0.3 or later.
- If immediate upgrade is not possible, disable XFF support in EVE configuration.
- Check OISF advisory and release guidance before applying production changes.
Validation and detection
- Inventory Suricata sensors and record installed versions.
- Review EVE configuration to determine whether XFF support is enabled.
- Confirm upgraded sensors report version 7.0.14, 8.0.3, or later.
- Monitor Suricata performance for abnormal slowdowns during HTTP alert processing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1050: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-22261 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L2.21.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OISF/suricata/security/advisories/GHSA-5jvg-5j3p-34cfCVE reference · x_refsource_CONFIRM
- https://github.com/OISF/suricata/commit/3f0725b34c7871c2de4346c8af872f10f4501e44CVE reference · x_refsource_MISC
- https://github.com/OISF/suricata/commit/af246ae7ab1b70c09f83c0619b253095ccc18667CVE reference · x_refsource_MISC
- https://redmine.openinfosecfoundation.org/issues/8156CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Excessive Platform Resource Consumption within a Loop
Excessive Platform Resource Consumption within a Loop represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.