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.
CVE-2020-5410
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 9.0(high)
- EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
June 2, 2020
Last Modified
November 3, 2025
Advisory Details (2)
Auto-updated Jun 4, 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-2020-5410CVE-2020-5410: Directory Traversal with spring-cloud-config-server
https://tanzu.vmware.com/security/cve-2020-5410Vendor Advisories for CVE-2020-5410(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | spring-cloud-config-server | 2021-08-11 | redhat |
| redhat | patch | 2020-12-16 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.springframework.cloud:spring-cloud-config-server | 2.2.0.RELEASE, 2.2.1.RELEASE, 2.2.2.RELEASE | 2.2.3 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 62× in last 7d / 227× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 400 total refreshes for this CVE.
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:00 UTCVendor advisory
- 2026-07-22 15:18 UTCEG score recompute
- 2026-07-22 15:18 UTCVendor advisory
- 2026-07-22 14:05 UTCEPSS rescore
- 2026-07-22 11:37 UTCVendor advisory
- 2026-07-22 07:55 UTCVendor advisory
- 2026-07-22 04:13 UTCVendor advisory
- 2026-07-22 00:18 UTCVendor advisory
- 2026-07-21 19:39 UTCVendor advisory
- 2026-07-21 15:57 UTCEG score recompute
- 2026-07-21 15:57 UTCVendor advisory
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 12:15 UTCVendor advisory
- 2026-07-21 08:34 UTCVendor advisory
- 2026-07-21 04:52 UTCVendor advisory
- 2026-07-21 01:12 UTCVendor advisory
- 2026-07-20 21:31 UTCVendor advisory
- 2026-07-20 17:50 UTCEG score recompute
- 2026-07-20 17:50 UTCVendor advisory
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 14:09 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-20 10:28 UTCVendor advisory
- 2026-07-20 06:47 UTCVendor advisory
- 2026-07-20 02:28 UTCVendor advisory
- 2026-07-19 22:46 UTCVendor advisory
- 2026-07-19 19:06 UTCVendor advisory
- 2026-07-19 15:25 UTCEG score recompute
- 2026-07-19 15:25 UTCVendor advisory
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 11:40 UTCVendor advisory
- 2026-07-19 07:59 UTCVendor advisory
- 2026-07-19 04:18 UTCVendor advisory
- 2026-07-19 00:36 UTCVendor advisory
- 2026-07-18 20:54 UTCVendor advisory
- 2026-07-18 17:13 UTCVendor advisory
- 2026-07-18 13:32 UTCEG score recompute
- 2026-07-18 13:32 UTCVendor advisory
- 2026-07-18 10:02 UTCEPSS rescore
- 2026-07-18 09:51 UTCVendor advisory
- 2026-07-18 06:09 UTCVendor advisory
- 2026-07-18 02:27 UTCVendor advisory
- 2026-07-17 22:46 UTCVendor advisory
- 2026-07-17 19:05 UTCVendor advisory
- 2026-07-17 15:24 UTCVendor advisory
- 2026-07-17 11:43 UTCVendor advisory
- 2026-07-17 08:01 UTCEG score recompute
- 2026-07-17 08:01 UTCVendor advisory
- 2026-07-17 04:19 UTCVendor advisory
- 2026-07-17 00:38 UTCVendor advisory
- 2026-07-16 20:58 UTCVendor advisory
- 2026-07-16 17:17 UTCVendor advisory
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 13:36 UTCVendor advisory
- 2026-07-16 09:55 UTCVendor advisory
- 2026-07-16 06:14 UTCVendor advisory
- 2026-07-16 02:32 UTCVendor advisory
- 2026-07-15 22:51 UTCVendor advisory
- 2026-07-15 19:10 UTCVendor advisory
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:29 UTCVendor advisory
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 11:49 UTCVendor advisory
- 2026-07-15 08:06 UTCVendor advisory
- 2026-07-15 04:25 UTCVendor advisory
- 2026-07-15 00:43 UTCVendor advisory
- 2026-07-14 21:01 UTCVendor advisory
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 17:21 UTCVendor advisory
- 2026-07-14 13:40 UTCVendor advisory
- 2026-07-14 09:59 UTCVendor advisory
- 2026-07-14 06:17 UTCVendor advisory
- 2026-07-14 02:37 UTCVendor advisory
- 2026-07-13 22:56 UTCVendor advisory
- 2026-07-13 19:15 UTCVendor advisory
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 15:34 UTCVendor advisory
- 2026-07-13 11:54 UTCVendor advisory
- 2026-07-13 08:13 UTCVendor advisory
- 2026-07-13 04:32 UTCVendor advisory
- 2026-07-13 00:51 UTCVendor advisory
- 2026-07-12 21:10 UTCVendor advisory
- 2026-07-12 17:28 UTCVendor advisory
- 2026-07-12 13:47 UTCVendor advisory
- 2026-07-12 10:05 UTCVendor advisory
- 2026-07-12 06:24 UTCVendor advisory
- 2026-07-12 02:43 UTCVendor advisory
- 2026-07-11 23:02 UTCVendor advisory
- 2026-07-11 19:21 UTCVendor advisory
- 2026-07-11 15:40 UTCVendor advisory
- 2026-07-11 11:59 UTCVendor advisory
- 2026-07-11 08:18 UTCVendor advisory
- 2026-07-11 04:37 UTCVendor advisory
- 2026-07-11 00:56 UTCVendor advisory
- 2026-07-10 21:13 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
Publicly available exploits
(3 references)Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCosamahamad/CVE-2020-5410-POCFirst seen Jun 16, 2020
CVE-2020-5410 Spring Cloud Config directory traversal vulnerability
Open source ↗ - Metasploitauxiliary/scanner/http/springcloud_directory_traversal✓ verifiedFirst seen Jun 1, 2020
Directory Traversal in Spring Cloud Config Server
Open source ↗ - Nucleihttp/cves/2020/CVE-2020-5410.yamlFirst seen Jan 1, 2020
Spring Cloud Config Server - Local File Inclusion
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Frequently asked(6)
What is CVE-2020-5410?
When was CVE-2020-5410 disclosed?
Is CVE-2020-5410 actively exploited?
What is the CVSS score of CVE-2020-5410?
Which products are affected by CVE-2020-5410?
How do I remediate CVE-2020-5410?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-5410
Is Your Infrastructure Affected by CVE-2020-5410?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.