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

Published Apr 24, 2026
·
Updated

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.

Affected Software

6 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 Db2 Genius Hub<=1.1, 1.1.1, 1.1.2
IBM Agentics<=1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade uuid to a version that resolves this vulnerability.

    Fixed in 14.0.0Patch Missing buffer bounds check in `v3`/`v5`/`v6` when `buf` is provided

Event History

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
Jul 13, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

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