CVE-2026-22263VulnerabilityPublished 27 Jan 2026

CVE-2026-22263: OISF suricata · Excessive Platform Resource Consumption within a Loop

Affects OISF suricataSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.0.3 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% 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:L

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

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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

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

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 suricata and 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.3 >=8.0.0	Fixed in 8.0.3

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

AI-suggested

European organizations should promptly upgrade Suricata installations to version 8.0.3 or later to remediate this vulnerability. Given the lack of known workarounds, patching is the primary mitigation strategy. Network administrators should audit their current Suricata versions and prioritize updates in environments with high HTTP/1 traffic volumes. Additionally, monitoring system resource usage and Suricata performance metrics can help detect potential exploitation attempts or resource exhaustion conditions. Implementing rate limiting or traffic shaping on HTTP/1 flows upstream may reduce the risk of triggering the vulnerability. Organizations should also ensure that their incident response teams are aware of this issue to quickly identify and respond to any abnormal Suricata behavior. Finally, maintaining robust network segmentation and layered security controls will help mitigate the impact if Suricata’s availability is compromised.

Description

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.

Impact

For European organizations, the primary impact of CVE-2026-22263 is the potential degradation of network security monitoring and intrusion prevention capabilities due to Suricata’s slowed processing. This can lead to delayed detection of malicious activity or network anomalies, increasing the risk of successful cyberattacks. Organizations with high network traffic volumes or those relying heavily on Suricata for real-time threat detection may experience significant performance bottlenecks, potentially causing partial denial of service of their security infrastructure. Critical sectors such as finance, telecommunications, energy, and government agencies in Europe, which often deploy Suricata for network defense, could see reduced situational awareness and slower incident response times. While the vulnerability does not directly expose sensitive data or allow unauthorized access, the availability impact can indirectly increase risk by impairing security operations.

CWE-1050Excessive Platform Resource Consumption within a Loop (opens in a new tab)
Base weakness
The product has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (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:50 UTC

WeaknessesCWE-1050

Technical details

References

Community reviews

Related threats