A vulnerability in the peering authentication in Cisco Catalyst SD-WAN Controller, formerly SD-WAN vSmart, Cisco Catalyst SD-WAN Manager, formerly SD-WAN vManage, and Cisco Catalyst SD-WAN Validator, formerly SD-WAN vBond, could allow an unauthenticated, remote attacker to bypass authentication and obtain administrative privileges on an affected system. This vulnerability exists because the peering authentication mechanism in an affected system is not working properly. An attacker could exploit this vulnerability by sending crafted requests to an affected system. A successful exploit could allow the attacker to log in to an affected Cisco Catalyst SD-WAN Controller as an internal, high-privileged, non-root user account. Using this account, the attacker could access NETCONF, which would then allow the attacker to manipulate network configuration for the SD-WAN fabric.
CVE-2026-20127
“—” beside the score: it is equal to NVD's CVSS score.
Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-02-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 10.0 retained for reference. Confidence: HIGH.
Also known asEUVD-2026-8675 (ENISA EUVD) · GHSA-p4cq-46q3-jr7w (GitHub Security Advisories)Source: ENISA EUVD
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALhigh confidence
- EG Risk
- 100EG Risk 100/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity100% × 45%Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high. - EPSS PROB
- 89%
- EPSS %ILE
- 99th
- KEV
- ⚠ Exploited
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 89% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.
No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.
The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Please 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.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://www.cisa.gov/news-events/directives/ed-26-03-mitigate-vulnerabilities-cisco-sd-wan-systems · https://www.cisa.gov/news-events/directives/supplemental-direction-ed-26-03-hunt-and-hardening-guidance-cisco-sd-wan-systems · https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa-EHchtZk · https://nvd.nist.gov/vuln/detail/CVE-2026-20127
Published
February 25, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Oct 30, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-20127Cisco Catalyst SD-WAN Controller Authentication Bypass Vulnerability
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-rpa-EHchtZkVendor Advisories for CVE-2026-20127(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 113× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 865 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 765 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-11-02 08:14 UTCEG score recompute
- 2026-11-02 08:14 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-11-01 09:38 UTCEG score recompute
- 2026-11-01 09:38 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-31 11:02 UTCEG score recompute
- 2026-10-31 11:01 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-30 12:25 UTCEG score recompute
- 2026-10-30 12:25 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-10-29 13:50 UTCEG score recompute
- 2026-10-29 13:49 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-28 15:14 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-27 16:38 UTCEG score recompute
- 2026-10-27 16:38 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-26 18:01 UTCEG score recompute
- 2026-10-26 18:01 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-10-25 19:23 UTCEG score recompute
- 2026-10-25 19:23 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-10-25 14:44 UTCEG score recompute
- 2026-10-24 20:47 UTCEG score recompute
- 2026-10-24 20:47 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-23 22:11 UTCEG score recompute
Show 75 moreShow fewer
- 2026-10-23 22:11 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 89% · 99th percentile
- 2026-10-22 23:33 UTCEG score recompute
- 2026-10-22 23:33 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-22 00:57 UTCEG score recompute
- 2026-10-22 00:57 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-21 02:21 UTCEG score recompute
- 2026-10-21 02:21 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-20 03:45 UTCEG score recompute
- 2026-10-20 03:45 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-19 05:08 UTCEG score recompute
- 2026-10-19 05:08 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-18 06:31 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-18 03:57 UTCEG score recompute
- 2026-10-17 07:55 UTCEG score recompute
- 2026-10-17 07:55 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-16 09:19 UTCEG score recompute
- 2026-10-16 09:19 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-15 10:41 UTCEG score recompute
- 2026-10-15 10:41 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-14 12:02 UTCEG score recompute
- 2026-10-14 12:02 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 13:25 UTCEG score recompute
- 2026-10-13 13:25 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 14:49 UTCEG score recompute
- 2026-10-12 14:48 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 05:15 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 01:02 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 20:52 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 20:06 UTCEG score recompute
- 2026-10-11 16:43 UTCEG score recompute
- 2026-10-11 16:43 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 14:51 UTCEG score recompute
- 2026-10-11 12:33 UTCEG score recompute
- 2026-10-11 12:33 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 08:23 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 04:13 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-11 00:02 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 19:53 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 15:43 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 11:32 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 07:22 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-10 03:13 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 23:03 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 18:53 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 14:43 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 10:30 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 06:19 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-09 02:10 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 22:00 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 17:50 UTCEG score recompute
- 2026-10-08 17:50 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-08 13:40 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 09:28 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 05:18 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-08 01:08 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 20:58 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 16:48 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 12:36 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 08:27 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 04:18 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-07 00:08 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 19:58 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 15:48 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 11:38 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 07:28 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 03:19 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-06 03:18 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 23:08 UTCGHSA enrichmentGHSA-p4cq-46q3-jr7w · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-05 18:57 UTCEG score recompute
Publicly available exploits
(6 references)Public exploit code is referenced for this CVE (1 Metasploit module, 5 GitHub PoCs). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.
- Metasploitauxiliary/admin/networking/cisco_sdwan_auth_bypass✓ verifiedPublished Apr 2, 2026
Cisco Catalyst SD-WAN Controller Authentication Bypass
Open source ↗ - Open source ↗GitHub PoCgigachadusers/cve-2026-20127Published Apr 15, 2026
- GitHub PoCsfewer-r7/CVE-2026-20127Published Mar 9, 2026
An exploit for the Cisco Catalyst SD-WAN Controller authentication bypass vulnerability, CVE-2026-20127
Open source ↗ - Open source ↗GitHub PoCyonathanpy/CVE-2026-20127-Cisco-SD-WAN-Preauth-RCEPublished Mar 7, 2026
- GitHub PoCBugFor-Pings/CVE-2026-20127_EXPPublished Mar 5, 2026
Cisco Catalyst SD-WAN 身份验证绕过漏洞(CVE-2026-20127)利用EXP
Open source ↗ - Open source ↗GitHub PoCzerozenxlabs/CVE-2026-20127---Cisco-SD-WAN-Preauth-RCEPublished Mar 4, 2026
Related CVEs(same CWE)
Frequently asked(6)
What is CVE-2026-20127?
When was the CVE record for CVE-2026-20127 published?
Is CVE-2026-20127 actively exploited?
What is the CVSS score of CVE-2026-20127?
Which products are affected by CVE-2026-20127?
How do I remediate CVE-2026-20127?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-20127
Is Your Infrastructure Affected by CVE-2026-20127?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.