Skip to main content
VulnerabilityPublished

CVE-2026-20054: Cisco Cyber Vision · Infinite Loop

Affects Cisco Cyber VisionSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.8 Medium · patch available : update Cisco Cyber Vision when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CiscoCisco Cyber VisionAffected
  • >=4.2.0 <4.3.0 – 5.3.2
54 affected builds
Fixed in–
CiscoCisco Secure Firewall Threat Defense (FTD) SoftwareAffected
  • 7.2.0 – 7.7.10.1
37 affected builds
Fixed in–
CiscoCisco UTD SNORT IPS Engine SoftwareAffected
  • 3.17.0S – 17.18.2
88 affected builds
Fixed in–

AI-suggested

Organizations should immediately identify and inventory all Cisco Cyber Vision deployments to determine if they run affected versions. Since no specific patch links are provided, contacting Cisco support or monitoring Cisco’s security advisories for official patches or updates is critical. In the interim, network segmentation and strict access controls should be enforced to limit exposure of Cisco Cyber Vision devices to untrusted networks, reducing the attack surface. Deploying intrusion prevention systems (IPS) or firewall rules to detect and block malformed VBA data packets targeting the Snort 3 Detection Engine may help mitigate exploitation attempts. Regularly monitoring system logs and detection engine health can provide early warning of attempted exploitation or crashes. Additionally, organizations should plan for rapid incident response to restore monitoring capabilities if a DoS event occurs. Finally, maintaining up-to-date backups and failover mechanisms for critical monitoring infrastructure will minimize operational disruption.

Description

Multiple Cisco products are affected by a vulnerability in the Snort 3 VBA feature that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to crash.&nbsp; This vulnerability is due to improper error checking when decompressing VBA data. An attacker could exploit this vulnerability by sending crafted VBA data to the Snort 3 Detection Engine on the targeted device. A successful exploit could allow the attacker to cause the Snort 3 Detection Engine to enter an infinite loop, causing a DoS condition.

References

Community reviews

Loading reviews…