CVE-2019-6976

libvips before 8.7.4 generates output images from uninitialized memory locations when processing corrupted input image data because iofuncs/memory.c does not zero out allocated memory. This can result in leaking raw process memory contents through the output image.

Published: 2019-01-26 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-6976 is rated Moderate Risk (51.6/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.30%). EPSS rose +2.03% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-6976

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.27% 2.30% +2.03%
2 2026-03-04 0.17% 0.27% +0.10%
3 2026-03-01 — 0.17% —

Full EPSS history (48 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-6976

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2019-6976

OS Trackers for CVE-2019-6976

vendor priority summary link
debian low CVE-2019-6976 low priority: Debian including 1 source packages (vips), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-6976
ubuntu medium CVE-2019-6976 medium priority: Ubuntu including 1 source packages (vips), 15 status rows across 15 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, trusty, upstream, xenial): not-affected 10, released 3, DNE 1, ignored 1. https://ubuntu.com/security/CVE-2019-6976

Affected software / configurations for CVE-2019-6976

Vendor Product Version Raw CPE
libvips libvips < 8.7.4 cpe:2.3:a:libvips:libvips:*:*:*:*:*:*:*:*

References for CVE-2019-6976

cvelogic Threat Intelligence