CVE-2026-41907 — uuid
CVE-2026-41907 is a Out-of-bounds Write vulnerability in uuid. A fix is available for uuid — see the affected versions and patch details below.
uuid: Missing buffer bounds check in `v3`/`v5`/`v6` when `buf` is provided
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41907.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
uuidnpmDescription
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | uuid | all versions | 11.1.1npm install uuid@11.1.1 |
| 📦npm | uuid | ≥ 12.0.0&&< 12.0.1 | 12.0.1npm install uuid@12.0.1 |
| 📦npm | uuid | ≥ 13.0.0&&< 13.0.1 | 13.0.1npm install uuid@13.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uuid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update uuid to 11.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41907 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-41907 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-41907. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This is a Moderate impact flaw. The `uuid` library, as used in Red Hat products, is susceptible to out-of-bounds writes when applications provide undersized external buffers for UUID generation. This can lead to data corruption or unintended information disclosure within the context of the vulnerable application, but…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Openshift Data Foundation 4.18 | odf4/cephcsi-rhel9:1786705347 | RHSA-2026:56431 |
| Red Hat Openshift Data Foundation 4.22 | odf4/cephcsi-rhel9:1787057250 | RHSA-2026:56928 |
Frequently Asked Questions
Is CVE-2026-41907 in your dependencies?
O3 Security finds CVE-2026-41907 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.