CVE-2020-6096
HIGHEPSS 92th pctlDescription
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.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
High risk: more likely to be exploited than 92% of all known CVEs.
References
Related Vulnerabilities
Other CWE-195 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-43663 | High | 8.1 | 14% | - | - |
| CVE-2011-3045 | High | 8.8 | 3.6% | - | Fix |
| CVE-2016-6560 | High | 8.6 | 1.7% | - | - |
| CVE-2023-3635 | Medium | 5.9 | 1.3% | - | Fix |
| CVE-2020-1913 | High | 8.1 | 1.2% | - | - |
| CVE-2026-26981 | Medium | 6.5 | 0.5% | - | Fix |
Common questions
How do I fix CVE-2020-6096?
Published advisories record a fix for 204 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2020-6096 being actively exploited?
Not that we know of. CVE-2020-6096 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 5.4% is the estimated probability that it will be exploited in the next 30 days. That is higher than 92% of all scored CVEs.
How severe is CVE-2020-6096?
CVE-2020-6096 has a CVSS v3 base score of 8.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2020-6096 affect?
Published advisories record a fix for glibc (Amazon), glibc-all-langpacks (Amazon), glibc-benchtests (Amazon), glibc-common (Amazon), and 200 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2020-6096
Markdown
[](https://tridentstack.com/cve/CVE-2020-6096)HTML
<a href="https://tridentstack.com/cve/CVE-2020-6096"><img src="https://tridentstack.com/cve/badge/CVE-2020-6096.svg" alt="CVE-2020-6096"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-17.