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

> The uuid library allows out-of-bounds writes when external buffers are provided, potentially leading to memory corruption or crashes.

- **Severity:** High 8.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** CLEANSTART-2026-FA47344, CLEANSTART-2026-SX19522, CLEANSTART-2026-ZG01610, CLSA-2026-1778805966, CLSA-2026-1782089806, CLSA-2026-1782089807, CLSA-2026-1782089809, CLSA-2026-1790718582, CLSA-2026-1790718709, CLSA-2026-1790718939, CLSA-2026-1790719328, CLSA-2026-1790767270, CLSA-2026-1792476235, CLSA-2026-1792477444, CLSA-2026-1793113739, DEBIAN-CVE-2026-41907, ECHO-6d25-1c6a-e331, MINI-3cg8-8g52-fmhc, MINI-3vwj-wq86-95r4, MINI-3wgc-q737-rv8v, MINI-4jq9-qgpv-j92r, MINI-66j5-fh6p-3g72, MINI-892p-2rr2-3jjg, MINI-8r6q-c4rr-8qv6, MINI-9mx2-382w-m39f, MINI-9qx9-w5wm-j3hr, MINI-c25j-5j8g-jwvc, MINI-fv6p-hwhc-hr5v, MINI-g9cv-jh86-8wvc, MINI-gg82-hrpm-2prw, MINI-h44v-6jcq-p62g, MINI-j4f3-qchh-6chh, MINI-jj6m-7424-hjcj, MINI-jjwf-jxc6-cgxm, MINI-jp3r-gr53-p7c6, MINI-m28r-ccjr-4rcc, MINI-m376-x253-hr5m, MINI-mq2v-9f8g-g9mm, MINI-r392-5gcw-6x26, MINI-r3v6-rgf7-cw2f, MINI-r58g-4c9h-634m, MINI-r72q-2r27-5799, MINI-vc4m-rpph-p5m9, MINI-vqh9-f63f-2v24, MINI-w6fp-p6qm-p33j, MINI-x7wm-wx22-9w36, MINI-xq7c-q25r-76rm, ROOT-APP-NPM-CVE-2026-41907, UBUNTU-CVE-2026-41907

## What is CVE-2026-41907?

CVE-2026-41907 is a high-severity memory corruption vulnerability in uuidjs uuid, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-823 (Use of Out-of-range Pointer Offset), CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-41907?

It affects 1 product.


Products: Uuidjs Uuid.

## How do I fix CVE-2026-41907?

Upgrade to a fixed version.

## Is CVE-2026-41907 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41907 exists.

## Other vulnerabilities in uuidjs uuid

- [CVE-2026-41988](https://insights.sbomify.com/CVE-2026-41988/): Memory corruption in uuid (low 3.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41907 and fix it if it is affected.

What it is: CVE-2026-41907 is a high-severity memory corruption vulnerability in uuidjs uuid, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41907 exists.

Affected product: uuidjs uuid. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41907/ (Markdown: https://insights.sbomify.com/CVE-2026-41907/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41907
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41907
- OSV: https://osv.dev/vulnerability/CVE-2026-41907

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41907/
Summaries are generated and may contain mistakes; the official description above is the record.