CVE-2026-41907: uuid: Missing buffer bounds check in `v3`/`v5`/`v6` when `buf` is provided
Summary
The v3(), v5(), and v6() API methods (not uuid release versions) accept external output buffers but do not reject out-of-range writes (small buf or large offset). By contrast, v4(), v1(), and v7() API methods explicitly throw RangeError on invalid bounds.
This inconsistency allows silent partial writes into caller-provided buffers.
Affected code
- src/v35.ts (v3()/v5() path) writes buf[offset + i] without bounds validation. - src/v6.ts writes buf[offset + i] without bounds validation.
Reproducible PoC
bash cd /home/StrawHat/uuid npm ci npm run build
node --input-type=module -e " import {v4,v5,v6} from './dist-node/index.js'; const ns='6ba7b810-9dad-11d1-80b4-00c04fd430c8'; for (const [name,fn] of [ ['v4()',()=>v4({},new Uint8Array(8),4)], ['v5()',()=>v5('x',ns,new Uint8Array(8),4)], ['v6()',()=>v6({},new Uint8Array(8),4)], ]) { try { fn(); console.log(name,'NOTHROW'); } catch(e){ console.log(name,'THREW',e.name); } }"
Observed:
- v4() THREW RangeError - v5() NOTHROW - v6() NOTHROW
Example partial overwrite evidence captured during audit:
text same true buf [ 170, 170, 170, 170, 75, 224, 100, 63 ] v6 [ 187, 187, 187, 187, 31, 19, 185, 64 ]
Security impact
- Primary: integrity/robustness issue (silent partial output). - If an application assumes full UUID writes into preallocated buffers, this can produce malformed/truncated/partially stale identifiers without error. - In systems where caller-controlled offsets/buffer sizes are exposed indirectly, this may become a security-relevant logic flaw.
Suggested fix
Add the same guard used by v4()/v1()/v7():
ts if (offset < 0 || offset + 16 > buf.length) { throw new RangeError(UUID byte range ${offset}:${offset + 15} is out of buffer bounds); }
Apply to:
- src/v35.ts (covers v3() and v5()) - src/v6.ts
Other sources
uuid is for the creation of RFC9562 (formerly RFC4122) UUIDs. Prior to 14.0.0, v3, v5, and v6 accept external output buffers but do not reject out-of-range writes (small buf or large offset). This allows silent partial writes into caller-provided buffers. This vulnerability is fixed in 14.0.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/node-uuidto a version that resolves this vulnerability.Fixed in 14.0.3-2 - Upgrade
Upgrade
npm/uuidto a version that resolves this vulnerability.Fixed in 11.1.1 - Upgrade
Upgrade
npm/uuidto a version that resolves this vulnerability.Fixed in 13.0.1 - Upgrade
Upgrade
npm/uuidto a version that resolves this vulnerability.Fixed in 12.0.1 - Upgrade
Upgrade
npm/uuidto a version that resolves this vulnerability.Fixed in 14.0.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41907?
CVE-2026-41907 is considered a critical vulnerability due to the potential for silent partial writes that can lead to data corruption.
How do I fix CVE-2026-41907?
To fix CVE-2026-41907, upgrade the uuid library to version 14.0.0 or later, which includes proper buffer bounds checks.
What software is affected by CVE-2026-41907?
CVE-2026-41907 affects versions of the npm/uuid library prior to 14.0.0.
What is the risk of not addressing CVE-2026-41907?
Not addressing CVE-2026-41907 can lead to serious security issues such as data corruption and application instability.
What are the implications of CVE-2026-41907 for developers?
Developers using the affected versions of the uuid library should implement the recommended update as soon as possible to prevent vulnerabilities in their applications.