CVE-2025-29918VulnerabilityPublished 10 Apr 2025Updated 3 Nov 2025

CVE-2025-29918: OISF suricata · Infinite Loop

Affects OISF suricataSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium : upgrade to 7.0.9 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.2Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.9

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

Attack Vector: Local
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: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
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 10 Apr 2025
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 7.0.9.

Affected software

Product	Affected	Fixed in
GitHuboisf/suricata`pkg:github/oisf/suricata`Other threats	Affected <7.0.9	Fixed in 7.0.9

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 to version 7.0.9 or later immediately to apply the fix for CVE-2025-29918. 2. Audit existing PCRE rules for the use of negated patterns that could potentially trigger infinite loops; avoid or rewrite such rules where possible. 3. Implement strict controls and validation on who can create or modify PCRE rules to prevent malicious or accidental introduction of problematic patterns. 4. Monitor Suricata process health and thread responsiveness to detect signs of infinite loops or hangs early, enabling rapid response. 5. In environments where inline mode is critical, consider deploying redundant Suricata instances or failover mechanisms to maintain network visibility during outages. 6. Incorporate Suricata version and rule integrity checks into regular security audits and patch management processes. 7. Educate network security teams about the risks associated with complex PCRE rules and the importance of testing rules in staging environments before production deployment.

Description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. A PCRE rule can be written that leads to an infinite loop when negated PCRE is used. Packet processing thread becomes stuck in infinite loop limiting visibility and availability in inline mode. This vulnerability is fixed in 7.0.9.

Impact

For European organizations, this vulnerability primarily threatens the availability of Suricata-based network security monitoring and intrusion prevention systems. In environments where Suricata operates inline to block or inspect traffic, an infinite loop in packet processing can cause the system to become unresponsive, leading to a denial of service. This can result in reduced network visibility, delayed detection of malicious activity, and potential exposure to attacks that would otherwise be blocked or logged. Critical sectors such as finance, energy, telecommunications, and government agencies that rely on Suricata for real-time threat detection may experience operational disruptions or increased risk of undetected intrusions. The impact is particularly severe in high-throughput networks where continuous monitoring is essential. Although confidentiality and integrity are not directly compromised, the loss of availability can indirectly facilitate further attacks by creating blind spots. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits targeting this vulnerability. European organizations must prioritize patching to maintain robust network defense capabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 21:08 UTC

WeaknessesCWE-835

Technical details

References

Community reviews

Related threats