CVE-2025-59147VulnerabilityPublished 1 Oct 2025

CVE-2025-59147: OISF suricata · Improperly Implemented Security Check for Standard

Affects OISF suricataSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 7.0.12 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.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.12

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

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

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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Oct 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.12.

Affected software

Product	Affected	Fixed in
OISF suricata	Affected <7.0.12	Fixed in 7.0.12

AI-suggested

To mitigate CVE-2025-59147, European organizations should prioritize upgrading Suricata to versions 7.0.12 or 8.0.1 or later, where the vulnerability is fixed. Network security teams must verify their Suricata deployment versions and plan immediate patching to eliminate the detection bypass risk. In parallel, organizations should review and enhance their network traffic monitoring to detect anomalous patterns indicative of SYN packet manipulation or session hijacking attempts. Deploying complementary network security tools that do not rely solely on Suricata for TCP session tracking can provide defense in depth. Additionally, organizations should implement strict network segmentation and enforce least privilege principles to limit the potential impact of undetected malicious traffic. Regular security audits and penetration testing should include attempts to exploit this vulnerability to validate the effectiveness of applied patches. Finally, maintaining up-to-date threat intelligence feeds and monitoring vendor advisories will help organizations respond quickly to any emerging exploit attempts.

Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Versions 7.0.11 and below, as well as 8.0.0, are vulnerable to detection bypass when crafted traffic sends multiple SYN packets with different sequence numbers within the same flow tuple, which can cause Suricata to fail to pick up the TCP session. In IDS mode this can lead to a detection and logging bypass. In IPS mode this will lead to the flow getting blocked. This issue is fixed in versions 7.0.12 and 8.0.1.

Impact

For European organizations, the impact of CVE-2025-59147 can be significant, especially for those relying on Suricata for network security monitoring and intrusion detection/prevention. In IDS deployments, attackers can craft network traffic to bypass detection, allowing malicious activities such as data exfiltration, lateral movement, or command and control communications to go unnoticed. This undermines the integrity of security monitoring and increases the risk of prolonged undetected breaches. In IPS deployments, the vulnerability may cause legitimate traffic flows to be blocked erroneously, potentially disrupting business-critical communications and causing availability issues. Organizations in sectors with high security requirements—such as finance, critical infrastructure, telecommunications, and government—may face increased risk of targeted attacks leveraging this bypass. Additionally, the inability to detect or properly log malicious traffic complicates incident response and forensic investigations. Given the network-based nature of the vulnerability and the widespread use of Suricata in European enterprises and public sector networks, the threat could affect a broad range of organizations if patches are not applied promptly.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Oct 2025, 19:36 UTC

WeaknessesCWE-358

Technical details

References

Community reviews

Related threats