Silent partial UUID writes via unchecked buffer bounds
Published Apr 24, 2026 · Updated Apr 24, 2026
Out-of-bounds writes in uuid before 11.1.1, uuid 12.0.0, and uuid 13.0.0 allow attackers to create malformed identifiers. The v3 and v5 path in src/v35.ts and v6 path in src/v6.ts write 16 bytes from a supplied offset without checking the offset's sign or remaining buffer capacity. Exploitation requires a consuming application to pass attacker-influenced buffer sizes or offsets, and the bounded consequence is silent partial or stale identifier output.
Summary
What happened
Out-of-bounds writes in uuid before 11.1.1, uuid 12.0.0, and uuid 13.0.0 allow attackers to create malformed identifiers. The v3 and v5 path in src/v35.ts and v6 path in src/v6.ts write 16 bytes from a supplied offset without checking the offset's sign or remaining buffer capacity. Exploitation requires a consuming application to pass attacker-influenced buffer sizes or offsets, and the bounded consequence is silent partial or stale identifier output.
The record
- CVE
- CVE-2026-41907
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- uuidjs
- Product
- uuid
- Classifications
- CWE-787, CWE-1285, CWE-823
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 14.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream reproducible buffer-bounds proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo