Packet-inspection interruption via incomplete RPC error checking
Published Mar 4, 2026 · Updated Mar 4, 2026
Incomplete RPC error checking in Cisco products using Snort 3 allows remote attackers to restart the detection engine with crafted RPC packets. The RPC parser performs incomplete error checking on data carried through an established connection and terminates the engine when crafted input reaches the faulty path. Snort 3 or the UTD engine must be installed and active; exploitation interrupts packet inspection until the engine restarts, without reported data disclosure or modification.
Summary
What happened
Incomplete RPC error checking in Cisco products using Snort 3 allows remote attackers to restart the detection engine with crafted RPC packets. The RPC parser performs incomplete error checking on data carried through an established connection and terminates the engine when crafted input reaches the faulty path. Snort 3 or the UTD engine must be installed and active; exploitation interrupts packet inspection until the engine restarts, without reported data disclosure or modification.
The record
- CVE
- CVE-2026-20068
- Published
- Mar 4, 2026
- Updated
- Mar 4, 2026
- Vendor
- ClamAV
- Product
- Cisco Cyber Vision
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2026CVE publishedPublication date reported by the CVE source.
- Mar 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0
- Affected versionversion=3.0.1
- Affected versionversion=3.0.2
- Affected versionversion=3.0.3
- Affected versionversion=3.0.4
- Affected versionversion=3.0.5
- Affected versionversion=3.0.6
- Affected versionversion=3.1.0
- Affected versionversion=3.1.1
- Affected versionversion=3.1.2
- Affected versionversion=3.2.0
- Affected versionversion=3.2.1
- Affected versionversion=3.2.2
- Affected versionversion=3.2.3
- Affected versionversion=3.2.4
- Affected versionversion=4.0.0
- Affected versionversion=4.0.1
- Affected versionversion=4.0.2
- Affected versionversion=4.0.3
- Affected versionversion=4.1.0
- Affected versionversion=4.1.1
- Affected versionversion=4.1.2
- Affected versionversion=4.1.3
- Affected versionversion=4.1.4
- Affected versionversion=4.1.5
- Affected versionversion=4.1.6
- Affected versionversion=4.1.7
- Affected versionversion=4.2.0
- Affected versionversion=4.2.1
- Affected versionversion=4.2.2
- Affected versionversion=4.2.3
- Affected versionversion=4.2.4
- Affected versionversion=4.2.6
- Affected versionversion=4.2.X
- Affected versionversion=4.3.0
- Affected versionversion=4.3.1
- Affected versionversion=4.3.2
- Affected versionversion=4.3.3
- Affected versionversion=4.4.0
- Affected versionversion=4.4.1
- Affected versionversion=4.4.2
- Affected versionversion=4.4.3
- Affected versionversion=5.0.0
- Affected versionversion=5.0.1
- Affected versionversion=5.0.2
- Affected versionversion=5.1.0
- Affected versionversion=5.1.1
- Affected versionversion=5.1.2
- Affected versionversion=5.1.3
- Affected versionversion=5.2.0
- Affected versionversion=5.2.1
- Affected versionversion=5.3.0
- Affected versionversion=5.3.1
- Affected versionversion=5.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo