
Cisco has published a critical Snort 3 security-hardening release covering four grouped CVEs across open-source software and Cisco products and services. The highest published base score is 9.0, and Cisco says there are no workarounds for affected self-managed releases.1
The two highest-scoring groups are CVE-2026-20043, covering out-of-bounds-write weaknesses, and CVE-2026-20236, covering incorrect-calculation weaknesses. Cisco grouped multiple internally discovered issues by weakness class, so the score represents the most severe underlying issue in each group rather than identical impact across every product.1
What administrators should decide
Separate Cisco-managed services from self-managed Snort 3 deployments. Cisco says its Cloud-delivered Firewall and Secure Access instances were automatically updated by October 21, and covered Meraki MX devices that were online and connected to the Meraki Dashboard were automatically updated. Self-managed Snort 3, Secure Firewall Threat Defense, Cyber Vision, and IOS XE UTD installations require exact release verification and, where vulnerable, an approved upgrade.1
Affected products
Cisco’s affected-product list spans Open Source Snort 3, Secure Firewall Threat Defense, Cyber Vision, Unified Threat Defense on IOS XE, Cloud-delivered Firewall, Secure Access, and covered Meraki MX security appliances.1
Snort 2 is not affected by this advisory, although Cisco notes that Snort 2 has reached end of life. Being outside this particular advisory is not a reason to keep an unsupported security engine in production.1
First fixed releases
Cisco’s product-specific table lists the following first fixed releases. Operators should confirm the currently supported target for their maintenance line rather than treating the minimum fixed build as a universal recommendation.1
| Product or branch | First fixed release |
|---|---|
| Open Source Snort 3.x | 3.12.4.0 |
| Cisco Cyber Vision | 5.6.0 |
| Secure Firewall Threat Defense 7.0 and earlier | 7.0.10 |
| Secure Firewall Threat Defense 7.2 | 7.2.12 |
| Secure Firewall Threat Defense 7.4 | 7.4.8 |
| Secure Firewall Threat Defense 7.6 | 7.6.6 |
| Secure Firewall Threat Defense 7.7 | 7.7.13 |
| Secure Firewall Threat Defense 10.0 / 10.1 | 10.0.2 / 10.1.0 |
| IOS XE UTD 17.12 / 17.15 / 17.18 | 17.12.8 / 17.15.6 / 17.18.5 |
| IOS XE UTD 26.1 / 26.2 | 26.1.2 / 26.2.1 |
What the 9.0 score means
The published vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. It describes the most severe grouped issue as network-reachable and unauthenticated, but high-complexity, with no user interaction required and potentially high confidentiality, integrity, and availability impact across a changed security scope.1
Cisco has not disclosed the exact attack mechanics for every underlying issue. This advisory supports urgent version checking and controlled remediation, but it does not by itself establish a working public exploit, internet exposure, or successful compromise of any specific system.1
Is it being exploited?
At the article’s October 21 reporting cutoff, Cisco said the vulnerabilities were found during internal testing and were not known to be actively exploited. That is a point-in-time vendor statement—not a guarantee that future exploitation will not occur.1
Practical guidance: a safe response sequence
The steps below are practical operational guidance derived from Cisco’s affected-product and fixed-release information; follow the applicable product’s installation documentation for the actual change.
- Identify where Snort 3 is actually running. Record product, exact software release, package origin, appliance/controller relationship, and whether Cisco manages the update path.
- Verify managed-service status. Do not generalize Cisco’s automatic-update statement to self-managed appliances or to Meraki devices that were offline or disconnected from the dashboard.
- Preserve configuration and recovery material. Export policy and configuration using the supported product workflow, document licenses and integrations, and prepare rollback without planning to restore a vulnerable build as the normal endpoint.
- Test the supported fixed target. Validate inspection policy, logging, alert delivery, throughput, fail-open/fail-closed behavior, and dependent network services.
- Confirm the running state afterward. Verify the fixed package or appliance build is active, stale workers are gone, traffic inspection still functions, and health and alert telemetry remain stable.
What this means for Treasure Coast businesses
The most relevant local exposure is a self-managed firewall, IDS/IPS, industrial-visibility platform, or IOS XE deployment that embeds Snort 3. A cloud-managed Cisco service may already be updated, but a locally administered appliance requires evidence from its own version and update state. If a managed IT provider operates the device, ask for the exact current release and the vendor advisory used to classify it.
What remains unknown
- The exact number and mechanics of the hidden issues grouped under each CVE.
- Whether public proof-of-concept code or private exploitation exists; Cisco reports no known active exploitation at cutoff.
- Whether every covered Meraki device was online and connected when the automatic update was applied.
- This article does not claim that any specific local organization is exposed or compromised.
Source
- Multiple Cisco Products Snort 3 Security Hardening Release: October 2026 — Cisco Security Advisory
cisco-sa-hardening-snort3-ybgmhTQe, published October 21, 2026. Read Cisco’s advisory. Accessed October 21, 2026.
