Cyber Resilience

CVE-2026-20058

Cisco Secure Firewall Threat Defense 7.2.0 … 7.7.10.1

Published
04 March 2026
Modified
20 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
EPSS Score 0.0039 32th percentile
Risk Priority 46 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-20058 is a medium-severity Access of Memory Location Before Start of Buffer (CWE-786) vulnerability in Cisco Secure Firewall Threat Defense. Its CVSS base score is 5.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Multiple Cisco products are affected by vulnerabilities in the Snort 3 VBA feature that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to crash. These vulnerabilities are due to improper error checking when decompressing VBA…

more

data. An attacker could exploit these vulnerabilities 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 unexpectedly restart, causing a DoS condition.

CWE(s)
CWE-786

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-20067Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20053Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20065Same product: Cisco Secure Firewall Threat Defense
CVE-2024-20363Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20066Same product: Cisco Secure Firewall Threat Defense
CVE-2024-20431Same product: Cisco Secure Firewall Threat Defense
CVE-2024-20508Same product: Cisco Unified Threat Defense Snort Intrusion Prevention System Engine
CVE-2026-20052Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20068Same product: Cisco Secure Firewall Threat Defense
CVE-2026-20057Same product: Cisco Secure Firewall Threat Defense

Affected Assets

cisco
snort
3.0.0-233 — 3.9.6.0
cisco
secure firewall threat defense
7.2.0, 7.2.0.1, 7.2.1, 7.2.10, 7.2.10.2
cisco
unified threat defense snort intrusion prevention system engine
17.12.1a, 17.12.2, 17.12.3, 17.12.3a, 17.12.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static/dynamic analysis can discover buffer-underflow conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of memory-safe constructs, bounds checking, and avoidance of pointer arithmetic that can produce underflow accesses.

SI-10 Information Input Validation partial match

Input validation rejects or sanitizes untrusted indices or offsets before they are used to compute buffer pointers.

SI-16 Memory Protection partial match

Memory-protection controls limit the effects of an out-of-bounds read/write even if the erroneous access occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent buffer underflows via safe coding, bounds checks, and analysis, but eliminating only this CWE covers a narrow slice of the control's broader intent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect and eliminate pre-buffer memory accesses before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes buffer-boundary checks that reduce out-of-bounds reads before buffer start.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate bounds checking and pointer validation to prevent pre-buffer accesses.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote safe memory handling and pointer arithmetic safeguards.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require bounds checking and pointer validation that prevent this weakness.

References