CVE-2026-22260VulnerabilityPublished 27 Jan 2026

CVE-2026-22260: OISF suricata · Uncontrolled Recursion

Affects OISF suricataSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 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 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.0.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade OISF suricata to 8.0.3.

Affected software

Product	Affected	Fixed in
OISFsuricata	Affected >=8.0.0 <8.0.3	Fixed in 8.0.3
GitHuboisf/suricata`pkg:github/oisf/suricata`Other threats	Affected =8.0.0 =8.0.3	Fixed in–

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

AI-suggested

1. Upgrade Suricata installations immediately to version 8.0.3 or later, where the vulnerability is patched. 2. If immediate upgrade is not feasible, revert the 'request-body-limit' and 'response-body-limit' configuration parameters to their default values to mitigate the uncontrolled recursion trigger. 3. Monitor Suricata logs and system stability closely for signs of crashes or abnormal behavior indicative of attempted exploitation. 4. Implement network-level filtering to restrict potentially malicious or malformed traffic that could trigger the recursion, especially from untrusted external sources. 5. Incorporate redundancy in IDS/IPS deployments to ensure continuous monitoring even if one instance crashes. 6. Regularly review and update IDS/IPS rules and configurations to minimize exposure to malformed packets. 7. Educate SOC personnel about this vulnerability and ensure incident response plans include procedures for Suricata service disruptions.

Description

Suricata is a network IDS, IPS and NSM engine. Starting in version 8.0.0 and prior to version 8.0.3, Suricata can crash with a stack overflow. Version 8.0.3 patches the issue. As a workaround, use default values for `request-body-limit` and `response-body-limit`.

Impact

The primary impact of CVE-2026-22260 is denial of service due to Suricata crashing from a stack overflow caused by uncontrolled recursion. For European organizations, this can result in temporary loss of network intrusion detection and prevention capabilities, increasing exposure to undetected cyber threats. Critical infrastructure sectors such as energy, finance, telecommunications, and government agencies that rely on Suricata for real-time network security monitoring are particularly vulnerable. A successful exploitation could disrupt security operations centers (SOCs) and delay incident detection and response, potentially allowing attackers to operate undetected. Since Suricata is often deployed at network perimeters or key monitoring points, its failure could degrade overall network security posture. The lack of confidentiality or integrity impact means data leakage or tampering is not a direct concern, but the availability impact alone is significant for maintaining continuous security monitoring.

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 18:05 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats