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)
- EG Risk
- 96(Attend)EG Risk 96/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 96%
- EPSS %ILE
- 100%
- 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(2)
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.
Data Freshness Timeline
(refreshed 51× in last 7d / 228× 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 823 total refreshes for this CVE.
- 2026-09-19 06:10 UTCVendor advisory
- 2026-09-19 02:28 UTCVendor advisory
- 2026-09-18 22:47 UTCVendor advisory
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 19:06 UTCVendor advisory
- 2026-09-18 15:25 UTCVendor advisory
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 11:44 UTCVendor advisory
- 2026-09-18 08:03 UTCVendor advisory
- 2026-09-18 04:22 UTCVendor advisory
- 2026-09-18 00:41 UTCVendor advisory
- 2026-09-17 21:00 UTCVendor advisory
- 2026-09-17 17:19 UTCVendor advisory
- 2026-09-17 13:35 UTCVendor advisory
- 2026-09-17 09:53 UTCVendor advisory
- 2026-09-17 06:13 UTCVendor advisory
- 2026-09-17 02:32 UTCVendor advisory
- 2026-09-16 22:49 UTCVendor advisory
- 2026-09-16 19:08 UTCVendor advisory
- 2026-09-16 15:28 UTCVendor advisory
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 11:46 UTCVendor advisory
- 2026-09-16 08:06 UTCEG score recompute
- 2026-09-16 08:06 UTCVendor advisory
- 2026-09-16 04:23 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-16 00:43 UTCVendor advisory
- 2026-09-15 21:02 UTCVendor advisory
- 2026-09-15 17:21 UTCVendor advisory
- 2026-09-15 13:40 UTCVendor advisory
- 2026-09-15 09:59 UTCVendor advisory
- 2026-09-15 06:18 UTCVendor advisory
- 2026-09-15 02:37 UTCVendor advisory
- 2026-09-14 22:56 UTCVendor advisory
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 19:15 UTCVendor advisory
- 2026-09-14 15:34 UTCVendor advisory
- 2026-09-14 11:53 UTCVendor advisory
- 2026-09-14 08:12 UTCVendor advisory
- 2026-09-14 04:32 UTCVendor advisory
- 2026-09-14 00:51 UTCVendor advisory
- 2026-09-13 21:10 UTCVendor advisory
- 2026-09-13 17:29 UTCVendor advisory
- 2026-09-13 13:48 UTCVendor advisory
- 2026-09-13 10:07 UTCVendor advisory
- 2026-09-13 06:26 UTCVendor advisory
- 2026-09-13 02:46 UTCVendor advisory
- 2026-09-12 23:05 UTCVendor advisory
- 2026-09-12 19:24 UTCVendor advisory
- 2026-09-12 15:43 UTCVendor advisory
- 2026-09-12 12:02 UTCVendor advisory
- 2026-09-12 08:21 UTCVendor advisory
- 2026-09-12 04:40 UTCVendor advisory
- 2026-09-12 00:59 UTCVendor advisory
- 2026-09-11 21:18 UTCVendor advisory
- 2026-09-11 18:49 UTCCISA KEV update
- 2026-09-11 17:38 UTCVendor advisory
- 2026-09-11 13:57 UTCVendor advisory
- 2026-09-11 10:15 UTCEG score recompute
- 2026-09-11 10:15 UTCVendor advisory
- 2026-09-11 06:34 UTCVendor advisory
- 2026-09-11 02:53 UTCVendor advisory
- 2026-09-10 23:12 UTCVendor advisory
- 2026-09-10 19:31 UTCVendor advisory
- 2026-09-10 19:28 UTCCISA KEV update
- 2026-09-10 15:50 UTCVendor advisory
- 2026-09-10 12:09 UTCVendor advisory
- 2026-09-10 08:28 UTCVendor advisory
- 2026-09-10 04:47 UTCVendor advisory
- 2026-09-10 01:06 UTCVendor advisory
- 2026-09-09 21:25 UTCVendor advisory
- 2026-09-09 19:08 UTCCISA KEV update
- 2026-09-09 17:42 UTCVendor advisory
- 2026-09-09 14:01 UTCVendor advisory
- 2026-09-09 10:20 UTCVendor advisory
- 2026-09-09 06:39 UTCVendor advisory
- 2026-09-09 02:58 UTCVendor advisory
- 2026-09-08 23:18 UTCEG score recompute
- 2026-09-08 23:18 UTCVendor advisory
- 2026-09-08 21:56 UTCEPSS rescore
- 2026-09-08 19:36 UTCVendor advisory
- 2026-09-08 18:54 UTCCISA KEV update
- 2026-09-08 15:56 UTCVendor advisory
- 2026-09-08 12:14 UTCVendor advisory
- 2026-09-08 08:29 UTCVendor advisory
- 2026-09-08 04:49 UTCVendor advisory
- 2026-09-08 01:07 UTCVendor advisory
- 2026-09-07 21:26 UTCVendor advisory
- 2026-09-07 17:46 UTCVendor advisory
- 2026-09-07 14:06 UTCVendor advisory
- 2026-09-07 10:23 UTCVendor advisory
- 2026-09-07 06:40 UTCVendor advisory
- 2026-09-07 03:00 UTCVendor advisory
- 2026-09-06 23:19 UTCVendor advisory
- 2026-09-06 19:39 UTCVendor advisory
- 2026-09-06 15:55 UTCEG score recompute
- 2026-09-06 15:55 UTCVendor advisory
- 2026-09-06 13:44 UTCEPSS rescore
- 2026-09-06 12:14 UTCVendor advisory
- 2026-09-06 08:32 UTCVendor advisory
- 2026-09-06 04:51 UTCVendor advisory
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
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
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.