Skip to content
vulnerability

CVE-2026-20128

7.5
High
KEV · Exploited in wildEPSS 7%Patch available

A vulnerability in the Data Collection Agent (DCA) feature of Cisco Catalyst SD-WAN Manager could allow an unauthenticated, remote attacker to gain DCA user privileges on an affected system. This vulnerability is due to the presence of a credential file for the DCA user on an affected system. An attacker could exploit this vulnerability by sending a crafted HTTP request and reading the file that contains the DCA password from that affected system. A successful exploit could allow the attacker to access another affected system and gain DCA user privileges. Note: Cisco Catalyst SD-WAN Manager releases 20.18 and later are not affected by this vulnerability.

exploited
Yes, in CISA KEV since 20 Apr 2026fix by 23 Apr 2026 (CISA deadline for US federal agencies)
fix
Patch available see the advisory in the references
likelihood
EPSS 7.3%
Published 25 Feb 2026Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstPlease adhere to CISA’s guidelines to assess exposure and mitigate risks associated with Cisco SD-WAN devices as outlines in CISA’s Emergency Directive 26-03 (URL listed below in Notes) and CISA’s “Hunt & Hardening Guidance for Cisco SD-WAN Devices (URL listed below in Notes). Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available.

triage
surface unknownruntimeWAF can block: noAV · localCWE-257· Common Weakness

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexityhighprivileges requiredhighuser interactionnonescopechangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
common questions

Is CVE-2026-20128 being exploited?

Yes. CVE-2026-20128 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-20128?

CVE-2026-20128 is rated High with a CVSS score of 7.5. 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-20128?

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

What does CVE-2026-20128 affect?

CVE-2026-20128 affects cisco:catalyst_sd-wan_manager. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

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

executive summary
technical analysis
affected
cisco:catalyst_sd-wan_manager
affected versions
Cisco Cisco Catalyst SD-WAN Manager
  • affected20.1.12
  • affected19.2.1
  • affected18.4.4
  • affected18.4.5
  • affected20.1.1.1
  • affected20.1.1
  • affected19.3.0
  • affected19.2.2
  • affected19.2.099
  • affected18.3.6
  • affected18.3.7
  • affected19.2.0
  • affected18.3.8
  • affected19.0.0
  • affected19.1.0
  • affected18.4.302
  • affected18.4.303
  • affected19.2.097
  • affected19.2.098
  • affected17.2.10
  • affected18.3.6.1
  • affected19.0.1a
  • affected18.2.0
  • affected18.4.3
  • affected18.4.1
  • affected17.2.8
  • affected18.3.3.1
  • affected18.4.0
  • affected18.3.1
  • affected17.2.6
  • affected17.2.9
  • affected18.3.4
  • affected17.2.5
  • affected18.3.1.1
  • affected18.3.5
  • affected18.4.0.1
  • affected18.3.3
  • affected17.2.7
  • affected18.3.0
  • affected19.2.3
  • affected18.4.501_ES
  • affected20.3.1
  • affected20.1.2
  • affected19.2.929
  • affected19.2.31
  • affected20.3.2
  • affected19.2.32
  • affected20.3.2.1
  • affected20.3.2.1_927
  • affected18.4.6
  • affected20.3.2_928
  • affected20.3.2_929
  • affected20.4.1.0.1
  • affected20.3.2.1_930
  • affected19.2.4
  • affected20.5.0.1.1
  • affected20.4.1.1
  • affected20.3.3
  • affected19.2.4.0.1
  • affected20.3.2_937
  • affected20.5.1
  • affected20.1.3
  • affected20.3.3.0.4
  • affected20.3.3.1.2
  • affected20.3.3.1.1
  • affected20.4.1.2
  • affected20.3.3.0.2
  • affected20.4.1.1.5
  • affected20.4.1.0.02
  • affected20.3.3.1.7
  • affected20.3.3.1.5
  • affected20.5.1.0.1
  • affected20.3.3.1.10
  • affected20.3.3.0.8
  • affected20.4.2
  • affected20.3.4
  • affected20.3.3.0.14
  • affected19.2.4.0.8
  • affected19.2.4.0.9
  • affected20.3.4.0.1
  • affected20.3.2.0.5
  • affected20.5.1.0.2
  • affected20.6.1.1
  • affected20.6.0.18.3
  • affected20.3.2.0.6
  • affected20.6.0.18.4
  • affected20.4.2.0.2
  • affected20.3.3.0.16
  • affected20.6.1.0.1
  • affected20.3.4.0.6
  • affected20.7.1EFT2
  • affected20.3.4.0.9
  • affected20.3.4.0.11
  • affected20.3.3.0.18
  • affected20.6.2.1
  • affected20.3.4.1
  • affected20.4.2.1
  • affected20.4.2.1.1
  • affected20.3.4.1.1
  • affected20.3.813
  • affected20.3.4.0.19
  • affected20.4.2.2.1
  • affected20.5.1.2
  • affected20.3.814
  • affected20.4.2.2
  • affected20.6.2.2
  • affected20.3.4.2.1
  • affected20.3.4.1.2
  • affected20.3.4.0.20
  • affected20.6.2.2.3
  • affected20.4.2.2.2
  • affected20.6.2.0.4
  • affected20.3.4.0.24
  • affected20.6.2.2.7
  • affected20.3.4.2.2
  • affected20.4.2.2.4
  • affected20.3.5.0.8
  • affected20.3.5.0.9
  • affected20.3.5.0.7
  • affected20.6.3.0.2
  • affected20.9.1EFT2
  • affected20.3.6
  • affected20.3.7
  • affected20.4.2.3
  • affected20.3.5.1
  • affected20.3.4.3
  • affected20.3.3.2
  • affected20.3.7.1
  • affected20.3.4.0.25
  • affected20.6.2.2.4
  • affected20.6.1.2
  • affected20.1.3.1
  • affected20.6.5.1.4
  • affected20.3.8
  • affected20.12.501
  • affected26.1.1

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.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 25 Feb 2026 (SSVC 2.0.3).

timeline

  1. 25 Feb 2026CISA SSVC assessment: exploitation active
  2. 25 Feb 2026Published · 1 day later
  3. 20 Apr 2026Added to CISA KEV (exploited in the wild) · 53 days later
  4. 21 Apr 2026CVE record last updated · 1 day later
  5. 23 Apr 2026CISA remediation due date (US federal agencies) · 2 days later
  6. 2 Nov 2026Analysed by vulneraibility.com · 194 days (about 6 months) later
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
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 2 links
  • Linksec.cloudapps.cisco.com /security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-authbp-qwCX8D4v
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-20128

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved