Skip to content
major vulnerability· requires attention

Critical CVSS 10.0 in Cisco Crosswork (widely used network automation); file-system control bug can broadly impact infrastructure and operations.

Networks

CVE-2026-20358

10.0
Critical
EPSS 0.46%Patch availableAug 20, 2026

Critical Cisco Crosswork file-system control flaw allows arbitrary file access.

common questions

Is CVE-2026-20358 being exploited?

Not confirmed. CVE-2026-20358 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.

How severe is CVE-2026-20358?

CVE-2026-20358 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-20358?

Yes. A fix has been recorded for CVE-2026-20358. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-20358 affect?

CVE-2026-20358 affects Cisco Crosswork (network automation). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-20358?

Install Cisco Crosswork security update immediately; restrict access and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Cisco Crosswork (network automation)
impact

Remote attackers can read/write arbitrary files, tamper configs, exfiltrate data, and potentially achieve code execution or disrupt services.

action required

Immediate action required

affected versions
Cisco Cisco Crosswork Planning
  • affected7.0.2
  • affected7.1.0
  • affected7.0.0
  • affected7.0.4
  • affected7.0.1
  • affected7.0.3
  • affected7.2.0
  • affected7.1.1
  • affected7.1.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free