CVE-2020-15123

CRITICALNVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 3.8%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 9.3Exploit: NoneExposed: 0

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

In codecov (npm package) before version 3.7.1 the upload method has a command injection vulnerability. Clients of the codecov-node library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE (CVE-2020-7597 for GHSA-5q88-cjfq-g2mh) was issued but the fix was incomplete. It only blocked &, and command injection is still possible using backticks instead to bypass the sanitizer. The attack surface is low in this case. Particularly in the standard use of codecov, where the module is used directly in a build pipeline, not built against as a library in another application that may supply malicious input and perform command injection.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

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 computed
Severity93% × 45%
Exploitation4% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
88.9%
KEV
Not listed

Published

July 20, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_commit, github_pr.
github Patch Available

Command injection in upload method · Advisory · codecov/codecov-node · GitHub

Affected: version 3.7.1

https://github.com/codecov/codecov-node/security/advisories/GHSA-xp63-6vf5-xf3v
github_pr Patch Available

Switch from execSync to execFileSync

Patch available: codecov/codecov-node v3.8.0 (PR #180 merged 2020-07-17)

https://github.com/codecov/codecov-node/pull/180
github_commit Patch Available

commit c0711c656686 (codecov/codecov-node)

Patch available: codecov/codecov-node v3.8.0 (contains commit c0711c656686)

https://github.com/codecov/codecov-node/commit/c0711c656686e902af2cd92d6aecc8074de4d83d
github Patch Available

codecov NPM module allows remote attackers to execute arbitrary commands · CVE-2020-7597 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-5q88-cjfq-g2mh

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
codecov—3.7.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 43× 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-23 14:15 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:49 UTCEG score recompute
  4. 2026-07-22 22:35 UTCEG score recompute
  5. 2026-07-22 14:05 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-19 14:28 UTCEPSS rescore
  10. 2026-07-19 14:28 UTCEPSS rescore
  11. 2026-07-19 08:22 UTCOSV refresh
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-18 10:02 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-16 16:59 UTCEPSS rescore
  17. 2026-07-15 16:55 UTCEPSS rescore
  18. 2026-07-13 22:27 UTCEPSS rescore
  19. 2026-07-12 05:44 UTCEPSS rescore
  20. 2026-07-11 08:24 UTCEPSS rescore
  21. 2026-07-09 19:06 UTCEPSS rescore
  22. 2026-07-08 15:11 UTCEPSS rescore
  23. 2026-07-07 13:43 UTCEPSS rescore
  24. 2026-07-06 16:25 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 72 more
  1. 2026-07-06 02:20 UTCEPSS rescore
  2. 2026-07-05 02:27 UTCEPSS rescore
  3. 2026-07-04 06:28 UTCEPSS rescore
  4. 2026-07-01 15:03 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-07-01 14:21 UTCOSV refresh
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-28 14:05 UTCEPSS rescore
  10. 2026-06-28 04:54 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-27 03:06 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-24 14:03 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-22 14:23 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 14:54 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
  26. 2026-06-19 19:23 UTCEPSS rescore
  27. 2026-06-18 17:50 UTCEPSS rescore
  28. 2026-06-18 17:50 UTCEPSS rescore
  29. 2026-06-17 17:50 UTCEPSS rescore
  30. 2026-06-17 17:50 UTCEPSS rescore
  31. 2026-06-16 17:50 UTCEPSS rescore
  32. 2026-06-16 17:50 UTCEPSS rescore
  33. 2026-06-15 17:46 UTCEPSS rescore
  34. 2026-06-14 23:15 UTCEPSS rescore
  35. 2026-06-14 23:15 UTCEPSS rescore
  36. 2026-06-13 22:58 UTCEPSS rescore
  37. 2026-06-13 22:58 UTCEPSS rescore
  38. 2026-06-13 22:43 UTCOSV refresh
  39. 2026-06-12 23:09 UTCEPSS rescore
  40. 2026-06-11 13:58 UTCEPSS rescore
  41. 2026-06-10 22:16 UTCEPSS rescore
  42. 2026-06-10 22:16 UTCEPSS rescore
  43. 2026-06-10 13:20 UTCEPSS rescore
  44. 2026-06-08 14:15 UTCEPSS rescore
  45. 2026-06-08 14:15 UTCEPSS rescore
  46. 2026-06-07 15:23 UTCEPSS rescore
  47. 2026-06-07 15:23 UTCEPSS rescore
  48. 2026-06-06 13:45 UTCEPSS rescore
  49. 2026-06-06 13:45 UTCEPSS rescore
  50. 2026-06-06 13:45 UTCEPSS rescore
  51. 2026-06-05 22:45 UTCEPSS rescore
  52. 2026-06-05 22:45 UTCEPSS rescore
  53. 2026-06-05 06:08 UTCEPSS rescore
  54. 2026-06-04 13:10 UTCEPSS rescore
  55. 2026-06-04 13:10 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-02 20:11 UTCEPSS rescore
  58. 2026-06-01 13:50 UTCEPSS rescore
  59. 2026-05-31 22:29 UTCEPSS rescore
  60. 2026-05-31 22:29 UTCEPSS rescore
  61. 2026-05-31 00:15 UTCEPSS rescore
  62. 2026-05-31 00:14 UTCEPSS rescore
  63. 2026-05-29 13:42 UTCEPSS rescore
  64. 2026-05-29 13:42 UTCEPSS rescore
  65. 2026-05-28 13:43 UTCEPSS rescore
  66. 2026-05-28 13:43 UTCEPSS rescore
  67. 2026-05-27 13:39 UTCEPSS rescore
  68. 2026-05-27 00:57 UTCEG score recompute
  69. 2026-05-26 13:42 UTCEPSS rescore
  70. 2026-05-26 13:42 UTCEPSS rescore
  71. 2026-05-26 07:17 UTCEPSS rescore
  72. 2026-05-26 07:17 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-15123?
CVE-2020-15123 is a critical vulnerability published on July 20, 2020. In codecov (npm package) before version 3.7.1 the upload method has a command injection vulnerability. Clients of the codecov-node library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability. A similar CVE (CVE-2020-7597 for GHSA-5q88-cjfq-g2mh) was…
When was CVE-2020-15123 disclosed?
CVE-2020-15123 was first published in the National Vulnerability Database on July 20, 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-15123 actively exploited?
CVE-2020-15123 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-15123?
CVE-2020-15123 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2020-15123?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-15123, 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-15123

Explore →

Is Your Infrastructure Affected by CVE-2020-15123?

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

Start Free Scan →Browse All CVEs