CVE-2020-5410

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.5 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild

Also known asEUVD-2020-0451 (ENISA EUVD) · GHSA-32xf-jwmv-9hf3 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 96%CVSS: 7.5Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
89
EG Risk 89/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low or medium mission impact; Act at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.
EPSS PROB
96%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.5 HIGH.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
96% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactAttend at low or medium mission impact; Act at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low or medium mission impact; Act at high (mission-essential systems).

A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2020-5410

Published

June 2, 2020

Last Modified

November 3, 2025

Advisory Details (2)

Auto-updated Oct 27, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa.
CISA🔴 Active Exploitation

Known 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-5410
Web page

Directory Traversal with spring-cloud-config-server

https://tanzu.vmware.com/security/cve-2020-5410

Vendor 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(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatspring-cloud-config-server2021-08-11redhat
redhatpatch2020-12-16redhat
mavenorg.springframework.cloud:spring-cloud-config-server @ 2.1.9 (fixes >= 2.1.0, < 2.1.9)—ghsa
mavenorg.springframework.cloud:spring-cloud-config-server @ 2.2.3 (fixes >= 2.2.0, < 2.2.3)—ghsa

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)
PackageVulnerable rangeFix by version rangeDependents
org.springframework.cloud:spring-cloud-config-server2.2.0.RELEASE, 2.2.1.RELEASE, 2.2.2.RELEASE
  • 2.1.0 up to 2.1.9: fixed in 2.1.9
  • 2.2.0 up to 2.2.3: fixed in 2.2.3
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 112× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 1,040 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 940 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 08:35 UTCGHSA enrichmentGHSA-32xf-jwmv-9hf3 · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-11-01 08:35 UTCEG score recompute
  3. 2026-11-01 06:33 UTCEG score recompute
  4. 2026-11-01 06:33 UTCVendor advisory
  5. 2026-10-31 05:19 UTCEG score recompute
  6. 2026-10-31 05:19 UTCVendor advisory
  7. 2026-10-30 04:05 UTCEG score recompute
  8. 2026-10-30 04:05 UTCVendor advisory
  9. 2026-10-29 02:51 UTCEG score recompute
  10. 2026-10-29 02:51 UTCVendor advisory
  11. 2026-10-28 01:38 UTCEG score recompute
  12. 2026-10-28 01:38 UTCVendor advisory
  13. 2026-10-27 16:28 UTCEPSS rescoreEPSS 96% · 99th percentile
  14. 2026-10-27 00:23 UTCEG score recompute
  15. 2026-10-27 00:23 UTCVendor advisory
  16. 2026-10-25 23:09 UTCVendor advisory
  17. 2026-10-25 18:41 UTCEG score recompute
  18. 2026-10-25 16:28 UTCEPSS rescoreEPSS 96% · 99th percentile
  19. 2026-10-24 21:55 UTCEG score recompute
  20. 2026-10-24 21:55 UTCVendor advisory
  21. 2026-10-23 20:42 UTCEG score recompute
  22. 2026-10-23 20:42 UTCVendor advisory
  23. 2026-10-23 16:28 UTCEPSS rescoreEPSS 96% · 99th percentile
  24. 2026-10-22 19:27 UTCEG score recompute
  25. 2026-10-22 19:27 UTCVendor advisory
Show 75 more
  1. 2026-10-21 18:14 UTCEG score recompute
  2. 2026-10-21 18:14 UTCVendor advisory
  3. 2026-10-20 17:01 UTCEG score recompute
  4. 2026-10-20 17:01 UTCVendor advisory
  5. 2026-10-20 16:28 UTCEPSS rescoreEPSS 96% · 99th percentile
  6. 2026-10-19 15:46 UTCEG score recompute
  7. 2026-10-19 15:46 UTCVendor advisory
  8. 2026-10-18 14:32 UTCVendor advisory
  9. 2026-10-18 09:19 UTCEG score recompute
  10. 2026-10-17 13:17 UTCEG score recompute
  11. 2026-10-17 13:17 UTCVendor advisory
  12. 2026-10-16 12:03 UTCEG score recompute
  13. 2026-10-16 12:03 UTCVendor advisory
  14. 2026-10-15 10:50 UTCEG score recompute
  15. 2026-10-15 10:50 UTCVendor advisory
  16. 2026-10-14 16:28 UTCEPSS rescoreEPSS 96% · 99th percentile
  17. 2026-10-14 09:33 UTCEG score recompute
  18. 2026-10-14 09:33 UTCVendor advisory
  19. 2026-10-13 08:20 UTCVendor advisory
  20. 2026-10-12 19:33 UTCEG score recompute
  21. 2026-10-12 07:06 UTCVendor advisory
  22. 2026-10-12 03:21 UTCVendor advisory
  23. 2026-10-11 23:36 UTCVendor advisory
  24. 2026-10-11 19:53 UTCEG score recompute
  25. 2026-10-11 19:53 UTCVendor advisory
  26. 2026-10-11 16:11 UTCEG score recompute
  27. 2026-10-11 16:11 UTCVendor advisory
  28. 2026-10-11 12:30 UTCEG score recompute
  29. 2026-10-11 12:30 UTCVendor advisory
  30. 2026-10-11 08:50 UTCVendor advisory
  31. 2026-10-11 05:07 UTCVendor advisory
  32. 2026-10-11 01:26 UTCVendor advisory
  33. 2026-10-10 21:45 UTCEG score recompute
  34. 2026-10-10 21:45 UTCVendor advisory
  35. 2026-10-10 19:56 UTCEPSS rescoreEPSS 96% · 99th percentile
  36. 2026-10-10 18:04 UTCVendor advisory
  37. 2026-10-10 14:23 UTCVendor advisory
  38. 2026-10-10 10:42 UTCVendor advisory
  39. 2026-10-10 07:01 UTCVendor advisory
  40. 2026-10-10 03:21 UTCVendor advisory
  41. 2026-10-09 23:40 UTCVendor advisory
  42. 2026-10-09 19:59 UTCVendor advisory
  43. 2026-10-09 16:18 UTCVendor advisory
  44. 2026-10-09 12:37 UTCVendor advisory
  45. 2026-10-09 08:55 UTCVendor advisory
  46. 2026-10-09 05:13 UTCVendor advisory
  47. 2026-10-09 01:32 UTCVendor advisory
  48. 2026-10-08 21:50 UTCVendor advisory
  49. 2026-10-08 18:09 UTCVendor advisory
  50. 2026-10-08 14:29 UTCVendor advisory
  51. 2026-10-08 10:47 UTCVendor advisory
  52. 2026-10-08 07:06 UTCVendor advisory
  53. 2026-10-08 03:25 UTCVendor advisory
  54. 2026-10-07 23:45 UTCEG score recompute
  55. 2026-10-07 23:45 UTCVendor advisory
  56. 2026-10-07 23:44 UTCEPSS rescoreEPSS 96% · 99th percentile
  57. 2026-10-07 20:03 UTCVendor advisory
  58. 2026-10-07 16:22 UTCVendor advisory
  59. 2026-10-07 12:38 UTCVendor advisory
  60. 2026-10-07 08:53 UTCVendor advisory
  61. 2026-10-07 05:12 UTCVendor advisory
  62. 2026-10-07 01:31 UTCVendor advisory
  63. 2026-10-06 21:50 UTCVendor advisory
  64. 2026-10-06 18:09 UTCVendor advisory
  65. 2026-10-06 14:28 UTCVendor advisory
  66. 2026-10-06 10:47 UTCVendor advisory
  67. 2026-10-06 07:07 UTCVendor advisory
  68. 2026-10-06 03:26 UTCVendor advisory
  69. 2026-10-06 03:25 UTCVendor advisory
  70. 2026-10-05 23:43 UTCVendor advisory
  71. 2026-10-05 20:00 UTCVendor advisory
  72. 2026-10-05 16:19 UTCVendor advisory
  73. 2026-10-05 12:39 UTCVendor advisory
  74. 2026-10-05 08:58 UTCVendor advisory
  75. 2026-10-05 05:18 UTCVendor advisory

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Metasploitauxiliary/scanner/http/springcloud_directory_traversal✓ verified
    Published Jul 6, 2020

    Directory Traversal in Spring Cloud Config Server

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-5410.yaml
    Published Jun 18, 2020

    Spring Cloud Config Server - Local File Inclusion

    Open source ↗
  • GitHub PoCosamahamad/CVE-2020-5410-POC
    Published Jun 16, 2020

    CVE-2020-5410 Spring Cloud Config directory traversal vulnerability

    Open source ↗

Frequently asked(6)

What is CVE-2020-5410?
CVE-2020-5410 is a critical-severity vulnerability; its CVE record was published on June 2, 2020. 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…
When was CVE-2020-5410 made public?
CVE-2020-5410 was made public on June 1, 2020: that is the date its CVE record's CNA, pivotal, gives for when the vulnerability was made public. The CVE record itself was published on June 2, 2020. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2020-5410 actively exploited?
Yes. CISA added CVE-2020-5410 to the Known Exploited Vulnerabilities catalog on March 25, 2022, affecting VMware Tanzu Spring Cloud Configuration (Config) Server. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2020-5410?
CVE-2020-5410 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2020-5410?
CVE-2020-5410 affects VMware Tanzu Spring Cloud Configuration (Config) Server. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2020-5410?
A fix for CVE-2020-5410 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-5410 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-5410

Explore →

Is Your Infrastructure Affected by CVE-2020-5410?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.