← console
voxell vciy

CVE-2021-1515: Cisco SD-WAN vManage Information Disclosure Vulnerability

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to sd-wan vmanage 20.4.1 or later upper bounds of the CVE record's affected ranges
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

A vulnerability in Cisco SD-WAN vManage Software could allow an unauthenticated, adjacent attacker to gain access to sensitive information. This vulnerability is due to improper access controls on API endpoints when Cisco SD-WAN vManage Software is running in multi-tenant mode. An attacker with access to a device that is managed in the multi-tenant environment could exploit this vulnerability by sending a request to an affected API endpoint on the vManage system. A successful exploit could allow the attacker to gain access to sensitive information that may include hashed credentials that could be used in future attacks.

weakness
CWE-284
affected
Cisco SD-WAN vManage
published ranges
cisco sd-wan vmanage < 20.4.1
first unaffected version, by branch
sd-wan vmanage 20.4.1
severity
4.3 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
assigned by
cisco
published
2021-05-06

check us tools.cisco.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
7 May 20210.00416
6 Jan 20220.0184
4 Feb 20220.01404
1 Apr 20220.00885
7 Mar 20230.0005scoring model v2023.03.01
8 Mar 20230.0005
11 Dec 20230.00051
20 Jan 20240.00058
19 Mar 20250.00064scoring model v2025.03.14
29 Mar 20250.00087
30 Mar 20250.00064
18 Nov 20250.00071
21 Nov 20250.00064
15 Jun 20260.00367scoring model v2026.06.15

14 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: sd-wan vmanage 20.4.1. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-1515', '2026-10-31T23:59:59.999999Z', now());