CVE-2020-6096

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity81% × 45%
Exploitation5% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
92%
KEV
Not listed

Published

April 1, 2020

Last Modified

November 21, 2024

References (14)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunscd (2.23-0ubuntu11.3) @ xenial2026-05-27ubuntu
ubuntulocales (2.34-0ubuntu3.2) @ impish2026-05-27ubuntu

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

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
glibc2.28-10, 2.28-10+deb10u12.28-10+deb10u2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
glibc—2.31-2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glibc—2.31-2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glibc—2.31-2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glibc—2.31-2—

Weakness Classification(3)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 24× 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 131 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2020-6096?
CVE-2020-6096 is a high vulnerability published on April 1, 2020. An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker…
When was CVE-2020-6096 disclosed?
CVE-2020-6096 was first published in the National Vulnerability Database on April 1, 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-6096 actively exploited?
CVE-2020-6096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 8.0% of all scored CVEs.
What is the CVSS score of CVE-2020-6096?
CVE-2020-6096 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2020-6096?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-6096, 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-6096

Explore →

Is Your Infrastructure Affected by CVE-2020-6096?

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

Start Free Scan →Browse All CVEs