CVE-2025-20360VulnerabilityPublished 15 Oct 2025Updated 12 Feb 2026

CVE-2025-20360: Cisco Cyber Vision · Buffer Access with Incorrect Length Value

Affects Cisco Cyber VisionSource CVE Database V5

Not known to be exploited · CVSS 5.8 Medium : upgrade to 4.3.0 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.8Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 15 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-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 Cisco Cyber Vision to 4.3.0.

Affected software

Product	Affected	Fixed in
Cisco Cisco Cyber Vision	Affected =3.0.0 =3.0.2 =3.0.3 =3.0.1 =3.1.0 =3.0.4 =3.1.1 =3.1.2 =3.2.0 =3.0.5 =3.2.1 =3.0.6 =3.2.2 =3.2.3 =3.2.4 =4.0.0 =4.0.1 =4.0.2 =4.0.3 =4.1.0 =4.1.1 =4.1.2 =4.1.3 =4.1.4 =4.2.0 =4.2.1 =4.1.5 =4.2.2 >=4.2.0 <4.3.0 =4.2.3 =4.2.4 =4.2.6 =4.1.6 =4.3.0 =4.3.1 =4.3.2 =4.3.3 =4.4.0 =4.4.1 =4.4.2 =4.4.3 =4.1.7 =5.0.0 =5.0.1 =5.0.2 =5.1.0 =5.1.1 =5.1.2 =5.1.3 =5.2.0 =5.2.1	Fixed in 4.3.0

AI-suggested

1. 2. If patches are not immediately available, implement network segmentation and access controls to limit exposure of Snort 3 components to untrusted networks. 3. Deploy strict firewall rules to restrict inbound HTTP traffic to only trusted sources and monitor for anomalous or malformed HTTP packets that could exploit the vulnerability. 4. Enable and review detailed logging on Cisco Cyber Vision to detect unusual restarts or HTTP parsing errors indicative of exploitation attempts. 5. Consider deploying additional intrusion detection or prevention systems to monitor for crafted HTTP traffic patterns targeting MIME fields. 6. Conduct regular vulnerability assessments and penetration testing focused on industrial network security tools to identify and remediate similar weaknesses. 7. Train security operations teams to recognize symptoms of Snort 3 Detection Engine restarts and respond promptly to minimize monitoring gaps. 8. Maintain an incident response plan that includes procedures for handling denial-of-service conditions affecting security monitoring infrastructure.

Description

Multiple Cisco products are affected by a vulnerability in the Snort 3 HTTP Decoder that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to restart. This vulnerability is due to a lack of complete error checking when the MIME fields of the HTTP header are parsed. An attacker could exploit this vulnerability by sending crafted HTTP packets through an established connection to be parsed by Snort 3. A successful exploit could allow the attacker to cause a DoS condition when the Snort 3 Detection Engine unexpectedly restarts.

Impact

For European organizations, especially those operating critical infrastructure, manufacturing, energy, and utilities sectors, this vulnerability could disrupt security monitoring capabilities by causing denial-of-service conditions in Cisco Cyber Vision deployments. The unexpected restart of the Snort 3 Detection Engine can create monitoring blind spots, increasing the risk of undetected malicious activity or network intrusions. This is particularly concerning in industrial control system (ICS) environments where continuous visibility is crucial for operational safety and compliance with regulations such as NIS2. The impact is limited to availability, with no direct compromise of confidentiality or integrity, but the loss of detection capability can indirectly facilitate further attacks. Organizations relying heavily on Cisco Cyber Vision for network security analytics may experience operational interruptions, delayed incident response, and increased risk exposure. Given the broad range of affected versions, many European enterprises may be vulnerable if patches are not applied promptly. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing the urgency for mitigation.

References

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-snort3-mime-vulns-tTL8PgVH (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Feb 2026, 06:40 UTC

Technical details

References

Community reviews

Related threats