CVE-2026-41907 affects the uuid package's v3(), v5(), and v6() UUID-generation APIs when caller-provided output buffers are supplied. Affected implementations fail to reject insufficient buffer capacity or excessive offsets, allowing silent partial writes rather than throwing a RangeError. This can produce malformed, truncated, or partially stale UUID values. The issue affects releases before 14.0.0, except for patched legacy releases 11.1.1, 12.0.1, and 13.0.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An out-of-range write vulnerability in the uuid library affecting versions prior to 14.0.0, where v3, v5, and v6 accept external output buffers without rejecting invalid buffer sizes or offsets, allowing silent partial writes into caller-provided buffers.
A vulnerability in the uuid package affecting calls to v3, v5, and v6 when buffer bounds are not properly verified, requiring package upgrades or explicit bounds checks to prevent unsafe operations.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.