No exploitation reported

CVE-2020-6096

No exploitation reported by the sources we read.

Published2020-04-01
WeaknessCWE-191 · CWE-195 · CWE-681

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC

2020-04-0122:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-6096?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-6096?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Fedoraproject fedora

Branch	Affected	Fixed in	Source
31.x	= 31	no fix published	NVD
32.x	= 32	no fix published	NVD

Debian debian linux

Branch	Affected	Fixed in	Source
10.0	= 10.0	no fix published	NVD

Gnu glibc

Branch	Affected	Fixed in	Source
2.31	≤ 2.31	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

CISA-ADPSSVC decisionnone2026-02-13
OpenCVESSVC decisionnone—
NVDCVSS 3.18.1read 2026-10-23
CNACVSS 3.08.1read 2026-10-23
NVDCVSS 2.06.8read 2026-10-23
CNAweakness (CWE)CWE-195read 2026-10-23
NVDweakness (CWE)CWE-191, CWE-681read 2026-10-23
FIRST EPSSEPSS score5.5 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2020-04-01
Last Modified: 2026-10-14
NVD status: Modified

Frequently asked questions

What is CVE-2020-6096?

Is CVE-2020-6096 actively exploited?

Active exploitation of CVE-2020-6096 has not been confirmed. Its EPSS score was 5.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-6096?

CVE-2020-6096 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database