CVE-2026-41988

uuid before 14.0.0 can make unexpected writes when external output buffers are used, and the UUID version is 3, 5, or 6. In particular, UUID version 4, which is very commonly used, is unaffected by this issue.

Published: 2026-04-23 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-41988 is rated Low Risk (13.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.11%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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-2026-41988

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.01% 0.11% +0.09%
2 2026-04-23 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41988

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.2 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.4 1.4 [email protected]

Weakness enumeration for CVE-2026-41988

OS Trackers for CVE-2026-41988

vendor priority summary link
debian not yet assigned CVE-2026-41988 not yet assigned priority: Debian including 1 source packages (node-uuid), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-41988
suse low — https://www.suse.com/security/cve/CVE-2026-41988/
ubuntu medium CVE-2026-41988 medium priority: Ubuntu including 1 source packages (node-uuid), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): needs-triage 9. https://ubuntu.com/security/CVE-2026-41988

Affected software / configurations for CVE-2026-41988

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-41988

cvelogic Threat Intelligence