← Back
CVE-2026-41907
high
CVSS 7.5
Vulnerability in uuid (CVE-2026-41907)
Summary
vulnerability in uuid (CVE-2026-41907). Data can be tampered with by attackers. Exploitable via ``uuid``. Mitigation: upgrade to `13.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41907** has been found in uuid.
Attackers can target a specific entry point like ``uuid`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade uuid to **13.0.1** or later.
If unsure, ask your IT team or search "uuid CVE-2026-41907" on the vendor's site.
CVE-2026-41907 (uuid) — CWE-1285 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `uuid` / `buf` / `offset` / `RangeError`
Patched: `13.0.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-1285) exists in uuid. Attackers reach the vulnerable code path via ``uuid`` without authentication.
📍 Affected scope
uuid — . Attack surface: `uuid` / `buf` / `offset` / `RangeError`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **13.0.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'uuid' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'uuid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `uuid` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade uuid to 13.0.1ステージング環境で 13.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
uuid
[{"type":"SEMVER","events":[{"introduced":"13.0.0"},{"fixed":"13.0.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41907
- package https://github.com/uuidjs/uuid
- web https://github.com/uuidjs/uuid/security/advisories/GHSA-w5hq-g745-h8pq
- web https://github.com/uuidjs/uuid/commit/3d2c5b0342f0fcb52a5ac681c3d47c13e7444b34
- web https://github.com/uuidjs/uuid/releases/tag/v14.0.0
- web https://github.com/uuidjs/uuid/commit/32389c887c9e75f90442ee4cc95bbab0c4e8346e
- web https://github.com/uuidjs/uuid/commit/3d61d6ac1f782cf6b1dd8661c60f11722cd49a0d
- web https://github.com/uuidjs/uuid/commit/9d27ddf7046ce496ef39569ff84d948eeff9cb2a
- web https://github.com/uuidjs/uuid/releases/tag/v11.1.1
- web https://github.com/uuidjs/uuid/releases/tag/v12.0.1
- web https://github.com/uuidjs/uuid/releases/tag/v13.0.1
- web https://github.com/advisories/GHSA-w5hq-g745-h8pq