CVE-2026-41907: uuid: Missing buffer bounds check in `v3`/`v5`/`v6` when `buf` is provided

Published Apr 22, 2026
·
Updated

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

9 affected componentsFixes available
npm/uuid<14.0.0
uuidjs Uuid Node.js<11.1.1
uuidjs Uuid Node.js=12.0.0
uuidjs Uuid Node.js=13.0.0
IBM SevOne Network Performance Management<=7.0.0 - 8.2.2
debian/node-uuid<=8.3.2+~8.3.3-3, <=8.3.2+~8.3.4-1
14.0.3-2
npm/uuid<11.1.1
11.1.1
npm/uuid>=13.0.0<13.0.1
13.0.1
npm/uuid>=12.0.0<12.0.1
12.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/node-uuid to a version that resolves this vulnerability.

    Fixed in 14.0.3-2
  2. Upgrade

    Upgrade npm/uuid to a version that resolves this vulnerability.

    Fixed in 11.1.1
  3. Upgrade

    Upgrade npm/uuid to a version that resolves this vulnerability.

    Fixed in 13.0.1
  4. Upgrade

    Upgrade npm/uuid to a version that resolves this vulnerability.

    Fixed in 12.0.1
  5. Upgrade

    Upgrade npm/uuid to a version that resolves this vulnerability.

    Fixed in 14.0.0

Event History

Apr 22, 2026
Advisory Published
via GitHub·08:53 PM
Data Sourced
via GitHub·08:53 PM
DescriptionSeverityWeaknessAffected Software
Apr 24, 2026
CVE Published
via MITRE·06:09 PM
Data Sourced
via MITRE·06:09 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software
Sep 26, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

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.

2

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.

3

What software is affected by CVE-2026-41907?

CVE-2026-41907 affects versions of the npm/uuid library prior to 14.0.0.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203