CVE-2020-5405

MEDIUMNVD 6.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 88% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 6.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
6.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS: 69%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, 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 a directory traversal attack.

CVSS v3
6.5
EG Score
9.0(high)
EPSS
99.3%
KEV
Not listed

Published

March 5, 2020

Last Modified

November 21, 2024

References (2)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework.cloud:spring-cloud-config-server2.2.0.RELEASE, 2.2.1.RELEASE2.2.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 32× 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.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:07 UTCEPSS rescore
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-04 06:29 UTCEPSS rescore
  6. 2026-07-04 06:29 UTCEPSS rescore
  7. 2026-07-02 07:17 UTCOSV refresh
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-06-30 23:20 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-28 14:05 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-25 13:48 UTCEPSS rescore
  15. 2026-06-25 13:48 UTCEPSS rescore
  16. 2026-06-24 14:03 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
Show 23 more
  1. 2026-06-15 17:46 UTCEPSS rescore
  2. 2026-06-14 23:15 UTCEPSS rescore
  3. 2026-06-14 07:43 UTCOSV refresh
  4. 2026-06-13 22:58 UTCEPSS rescore
  5. 2026-06-13 22:58 UTCEPSS rescore
  6. 2026-06-12 23:10 UTCEPSS rescore
  7. 2026-06-12 23:10 UTCEPSS rescore
  8. 2026-06-10 22:16 UTCEPSS rescore
  9. 2026-06-10 13:20 UTCEPSS rescore
  10. 2026-06-05 22:45 UTCEPSS rescore
  11. 2026-06-05 22:45 UTCEPSS rescore
  12. 2026-06-01 13:50 UTCEPSS rescore
  13. 2026-05-31 22:29 UTCEPSS rescore
  14. 2026-05-31 22:29 UTCEPSS rescore
  15. 2026-05-31 00:15 UTCEPSS rescore
  16. 2026-05-31 00:15 UTCEPSS rescore
  17. 2026-05-29 13:42 UTCEPSS rescore
  18. 2026-05-28 13:43 UTCEPSS rescore
  19. 2026-05-28 13:43 UTCEPSS rescore
  20. 2026-05-27 06:59 UTCEG score recompute
  21. 2026-05-26 07:17 UTCEPSS rescore
  22. 2026-05-26 07:17 UTCEPSS rescore
  23. 2026-05-25 21:46 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2020/CVE-2020-5405.yaml
    First seen Jan 1, 2020

    Spring Cloud Config - Local File Inclusion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-5405?
CVE-2020-5405 is a medium vulnerability published on March 5, 2020. Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, 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-5405 disclosed?
CVE-2020-5405 was first published in the National Vulnerability Database on March 5, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-5405 actively exploited?
CVE-2020-5405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-5405?
CVE-2020-5405 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2020-5405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-5405, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2020-5405?

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

Start Free Scan →Browse All CVEs