CVE Intelligence
CISA KEV High File handling

CVE-2020-5410 — VMware Tanzu Spring Cloud Config Directory Traversal Vulnerability

Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack.

Published Jun 2, 2020 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: pivotal

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (nuclei, metasploit, github)+20
  • EPSS 95.6% (30-day exploitation probability)+15
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 25, 2022
EPSS FIRST
95.59%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Spring by VMware
Spring Cloud Config and 1 more
CVSS base
7.5
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Org.springframework.cloud:spring-cloud-config-server: fixed in version 2.1.9 — github.com (GitHub Security Advisories)
  • Maven Org.springframework.cloud:spring-cloud-config-server: fixed in version 2.2.3 — github.com (GitHub Security Advisories)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Apr 15, 2022 — passed 1644 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Spring by VMware Spring Cloud Config, Vmware Spring Cloud Config, Maven Org.springframework.cloud:spring-cloud-config-server).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. Apply the fixed version or the patch documented under Remediation.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Spring by VMware Spring Cloud Config ≥ 2.1 and < 2.1.9≥ 2.2 and < 2.2.3 Vulnerable CVE Program (cve.org) e CISA ADP
Vmware Spring Cloud Config ≥ 2.1.0 and < 2.1.9≥ 2.2.0 and < 2.2.3 Vulnerable NIST National Vulnerability Database
Maven Org.springframework.cloud:spring-cloud-config-server ≥ 2.1.0 and < 2.1.9≥ 2.2.0 and < 2.2.3 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 25, 2022
Federal deadline
Apr 15, 2022
passed 1644 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules
Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 95.59%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor file creation in web directories and paths with traversal sequences (../).
  • Hunt retroactively in logs from before Mar 25, 2022 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.springframework.cloud:spring-cloud-config-server
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · spring by vmware/spring cloud config
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · vmware/spring cloud config
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    Mar 24, 2022 · CISA
  • 2020
  • CVE published
    Jun 2, 2020 · pivotal

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Spring by VMware
every CVE for this vendor
2022-03
what else CISA listed that month
File handling
same class
CWE-22
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-59315 Uncontrolled Resource Consumption in Vmware Spring Cloud Config Aug 27, 2026
  • High CVE-2026-47894 Spring Cloud Config Server native environment repository allows exposure of… Aug 27, 2026
  • High CVE-2026-47836 TOCTOU Race Condition in Vmware Spring Cloud Config Aug 26, 2026
  • Critical CVE-2026-47837 Missing Authentication for Critical Function in Vmware Spring Cloud Config Aug 26, 2026
  • High CVE-2026-41002 TOCTOU Race Condition in Vmware Spring Cloud Config May 7, 2026
  • Medium CVE-2026-41004 Insertion of Sensitive Information into Log File in Vmware Spring Cloud Config May 7, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-5410 is "VMware Tanzu Spring Cloud Config Directory Traversal Vulnerability", rated High. It affects Spring Cloud Config (Spring by VMware); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.5 describes technical severity. EPSS 95.59% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.