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 53× in last 7d / 226× 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 639 total refreshes for this CVE.
- 2026-08-26 02:35 UTCVendor advisory
- 2026-08-25 22:53 UTCVendor advisory
- 2026-08-25 19:12 UTCVendor advisory
- 2026-08-25 15:31 UTCEG score recompute
- 2026-08-25 15:31 UTCVendor advisory
- 2026-08-25 11:50 UTCVendor advisory
- 2026-08-25 08:09 UTCVendor advisory
- 2026-08-25 04:25 UTCVendor advisory
- 2026-08-25 00:44 UTCVendor advisory
- 2026-08-24 21:04 UTCVendor advisory
- 2026-08-24 18:52 UTCCISA KEV update
- 2026-08-24 17:23 UTCEG score recompute
- 2026-08-24 17:23 UTCVendor advisory
- 2026-08-24 13:43 UTCVendor advisory
- 2026-08-24 10:02 UTCEG score recompute
- 2026-08-24 10:02 UTCVendor advisory
- 2026-08-24 06:21 UTCVendor advisory
- 2026-08-24 02:40 UTCVendor advisory
- 2026-08-23 22:55 UTCVendor advisory
- 2026-08-23 19:15 UTCVendor advisory
- 2026-08-23 15:34 UTCVendor advisory
- 2026-08-23 11:54 UTCVendor advisory
- 2026-08-23 08:13 UTCVendor advisory
- 2026-08-23 04:32 UTCVendor advisory
- 2026-08-23 00:52 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-22 21:11 UTCVendor advisory
- 2026-08-22 17:29 UTCVendor advisory
- 2026-08-22 13:48 UTCVendor advisory
- 2026-08-22 10:07 UTCVendor advisory
- 2026-08-22 06:26 UTCVendor advisory
- 2026-08-22 02:45 UTCVendor advisory
- 2026-08-21 23:05 UTCVendor advisory
- 2026-08-21 19:24 UTCVendor advisory
- 2026-08-21 16:49 UTCCISA KEV update
- 2026-08-21 15:43 UTCVendor advisory
- 2026-08-21 12:02 UTCVendor advisory
- 2026-08-21 08:22 UTCVendor advisory
- 2026-08-21 04:41 UTCVendor advisory
- 2026-08-21 01:00 UTCVendor advisory
- 2026-08-20 21:19 UTCVendor advisory
- 2026-08-20 17:39 UTCVendor advisory
- 2026-08-20 17:06 UTCCISA KEV update
- 2026-08-20 13:58 UTCVendor advisory
- 2026-08-20 10:17 UTCVendor advisory
- 2026-08-20 06:37 UTCVendor advisory
- 2026-08-20 02:56 UTCVendor advisory
- 2026-08-19 23:15 UTCVendor advisory
- 2026-08-19 19:34 UTCVendor advisory
- 2026-08-19 17:33 UTCCISA KEV update
- 2026-08-19 15:53 UTCVendor advisory
- 2026-08-19 12:13 UTCVendor advisory
- 2026-08-19 08:32 UTCVendor advisory
- 2026-08-19 04:50 UTCVendor advisory
- 2026-08-19 01:10 UTCVendor advisory
- 2026-08-18 21:27 UTCVendor advisory
- 2026-08-18 17:38 UTCVendor advisory
- 2026-08-18 16:58 UTCCISA KEV update
- 2026-08-18 13:58 UTCVendor advisory
- 2026-08-18 10:15 UTCVendor advisory
- 2026-08-18 06:34 UTCVendor advisory
- 2026-08-18 02:53 UTCVendor advisory
- 2026-08-17 23:12 UTCVendor advisory
- 2026-08-17 19:31 UTCVendor advisory
- 2026-08-17 15:50 UTCVendor advisory
- 2026-08-17 13:56 UTCCISA KEV update
- 2026-08-17 12:09 UTCVendor advisory
- 2026-08-17 08:28 UTCVendor advisory
- 2026-08-17 04:48 UTCVendor advisory
- 2026-08-17 01:07 UTCVendor advisory
- 2026-08-16 21:26 UTCVendor advisory
- 2026-08-16 17:45 UTCEG score recompute
- 2026-08-16 17:45 UTCVendor advisory
- 2026-08-16 14:52 UTCEPSS rescore
- 2026-08-16 14:04 UTCVendor advisory
- 2026-08-16 10:23 UTCVendor advisory
- 2026-08-16 06:42 UTCVendor advisory
- 2026-08-16 03:02 UTCVendor advisory
- 2026-08-15 23:22 UTCVendor advisory
- 2026-08-15 19:41 UTCVendor advisory
- 2026-08-15 16:00 UTCVendor advisory
- 2026-08-15 12:19 UTCVendor advisory
- 2026-08-15 08:38 UTCVendor advisory
- 2026-08-15 04:57 UTCVendor advisory
- 2026-08-15 01:16 UTCVendor advisory
- 2026-08-14 21:36 UTCVendor advisory
- 2026-08-14 17:55 UTCVendor advisory
- 2026-08-14 14:15 UTCVendor advisory
- 2026-08-14 10:34 UTCVendor advisory
- 2026-08-14 06:54 UTCVendor advisory
- 2026-08-14 03:13 UTCVendor advisory
- 2026-08-13 23:33 UTCEG score recompute
- 2026-08-13 23:33 UTCVendor advisory
- 2026-08-13 21:57 UTCEPSS rescore
- 2026-08-13 19:52 UTCVendor advisory
- 2026-08-13 16:11 UTCVendor advisory
- 2026-08-13 12:30 UTCVendor advisory
- 2026-08-13 08:50 UTCVendor advisory
- 2026-08-13 05:09 UTCVendor advisory
- 2026-08-13 01:28 UTCVendor advisory
- 2026-08-12 21:48 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 p98HIGH
- 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.