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

Q: How do I fix CVE-2020-5410?

spring cloud config: upgrade to 2.1.9, 2.2.3. Exact commands for each OS are on this page.

Q: Is CVE-2020-5410 being exploited?

Yes. CVE-2020-5410 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

Q: What does CVE-2020-5410 affect?

CVE-2020-5410 affects spring cloud config. Severity is high (CVSS 7.5). 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

Q: How urgent is CVE-2020-5410?

Priority 86/100. High severity; EPSS top 1%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; Remotely exploitable, no login, no user action

Patch now

HIGH 7.5EXPLOITEDREMOTEUPGRADE

CVE-2020-5410 is a high-severity flaw (CVSS 7.5) affecting spring cloud config, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
EPSS top 1%: very likely to be exploited
Exploited in the wild (CISA KEV)
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	95.6% (top 1%)
CISA exploited list	Yes, fix due 2022-04-15
Weakness	CWE-23, CWE-22
Published	2020-06-02
Last modified	2026-06-17

Publisher (CNA): Pivotal Software, Inc. · Vendor: vmware

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-06-02 17:15 UTCPublished CVE record published
2022-03-25Exploited Added to the CISA Known Exploited Vulnerabilities list
2022-04-15Deadline CISA due date for US federal agencies to patch
2026-06-17 03:21 UTCUpdated Record last modified

vmware spring cloud config UPGRADE

Affected: >= 2.1.0 and < 2.1.9 · >= 2.2.0 and < 2.2.3

Fixed in: 2.1.9, 2.2.3

Safe to downgrade to: a release before 2.1.0

1. Check installed version

apt-cache policy spring-cloud-config || rpm -q spring-cloud-config || spring-cloud-config --version

2. UPGRADE to 2.1.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-cloud-config

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-cloud-config

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.1.0 (Debian / Ubuntu)

apt-cache madison spring-cloud-config sudo apt install spring-cloud-config=<VERSION_BEFORE_2.1.0> sudo apt-mark hold spring-cloud-config

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-cloud-config sudo dnf downgrade spring-cloud-config-<VERSION_BEFORE_2.1.0> sudo dnf versionlock add spring-cloud-config

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Maven · org.springframework.cloud:spring-cloud-config-server · FIXED · 2.1.9 · vulnerable: >= 2.1.0, < 2.1.9 · source

Set org.springframework.cloud:spring-cloud-config-server to 2.1.9 or later in pom.xml or build.gradle, then rebuild and redeploy.

Fedora 46 · feh · FIXED · 3.13.1-1.fc46 · FEDORA-2026-3c76a13a4f · source

sudo dnf upgrade --advisory=FEDORA-2026-3c76a13a4f

Fedora ELN · setroubleshoot · FIXED · 3.3.37-7.eln159 · FEDORA-2026-f81b122fe1 · source

sudo dnf upgrade --advisory=FEDORA-2026-f81b122fe1

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: dead5nd/config-demo (0 stars)
GitHub PoC: shoucheng3/spring-cloud__spring-cloud-config_CVE-2020-5410_2-1-8-RELEASE (0 stars)
GitHub PoC: Live-Hack-CVE/CVE-2020-5410
GitHub PoC: mugisyahid/ki-vuln-cve-2020-5410
Metasploit: Directory Traversal in Spring Cloud Config Server
Nuclei scan template: Spring Cloud Config Server - Local File Inclusion

Verify at the official source NVD · CVE Program · CISA KEV catalog · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5410?

spring cloud config: upgrade to 2.1.9, 2.2.3. Exact commands for each OS are on this page.

Is CVE-2020-5410 being exploited?

Yes. CVE-2020-5410 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.

What does CVE-2020-5410 affect?

CVE-2020-5410 affects spring cloud config. Severity is high (CVSS 7.5). 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

How urgent is CVE-2020-5410?

Priority 86/100. High severity; EPSS top 1%: very likely to be exploited; Exploited in the wild (CISA KEV); Public exploit reference; Remotely exploitable, no login, no user action

Software pages

VMware vulnerabilities

Related CVEs

CVE-2026-40982 CRITICAL 9.1 UPGRADE Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-conf
CVE-2026-40981 HIGH 7.5 UPGRADE When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request
CVE-2026-41002 HIGH 7.2 UPGRADE The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone
CVE-2026-41004 MEDIUM 4.4 UPGRADE When enabling trace logging in Spring Cloud Config Server sensitive information was placed in plain text in th
CVE-2026-22739 HIGH 8.6 UPGRADE Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud

References

← Back to latest CVEs