Skip to content

Update dependency uuid to v11 [SECURITY]#706

Open
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/npm-uuid-vulnerability
Open

Update dependency uuid to v11 [SECURITY]#706
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/npm-uuid-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 23, 2026

This PR contains the following updates:

Package Change Age Confidence
uuid ^9.0.1^11.0.0 age confidence

uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided

CVE-2026-41907 / GHSA-w5hq-g745-h8pq

More information

Details

Summary

The v3(), v5(), and v6() API methods (not uuid release versions) accept external output buffers but do not reject out-of-range writes (small buf or large offset).
By contrast, v4(), v1(), and v7() API methods explicitly throw RangeError on invalid bounds.

This inconsistency allows silent partial writes into caller-provided buffers.

Affected code
  • src/v35.ts (v3()/v5() path) writes buf[offset + i] without bounds validation.
  • src/v6.ts writes buf[offset + i] without bounds validation.
Reproducible PoC
cd /home/StrawHat/uuid
npm ci
npm run build

node --input-type=module -e "
import {v4,v5,v6} from './dist-node/index.js';
const ns='6ba7b810-9dad-11d1-80b4-00c04fd430c8';
for (const [name,fn] of [
  ['v4()',()=>v4({},new Uint8Array(8),4)],
  ['v5()',()=>v5('x',ns,new Uint8Array(8),4)],
  ['v6()',()=>v6({},new Uint8Array(8),4)],
]) {
  try { fn(); console.log(name,'NO_THROW'); }
  catch(e){ console.log(name,'THREW',e.name); }
}"

Observed:

  • v4() THREW RangeError
  • v5() NO_THROW
  • v6() NO_THROW

Example partial overwrite evidence captured during audit:

same true buf [
  170, 170, 170, 170,
   75, 224, 100,  63
]
v6 [
  187, 187, 187, 187,
   31,  19, 185,  64
]
Security impact
  • Primary: integrity/robustness issue (silent partial output).
  • If an application assumes full UUID writes into preallocated buffers, this can produce malformed/truncated/partially stale identifiers without error.
  • In systems where caller-controlled offsets/buffer sizes are exposed indirectly, this may become a security-relevant logic flaw.
Suggested fix

Add the same guard used by v4()/v1()/v7():

if (offset < 0 || offset + 16 > buf.length) {
  throw new RangeError(`UUID byte range ${offset}:${offset + 15} is out of buffer bounds`);
}

Apply to:

  • src/v35.ts (covers v3() and v5())
  • src/v6.ts

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

uuidjs/uuid (uuid)

v11.1.1

Compare Source

v11.1.0

Compare Source

Features
  • update TS types to allowUint8Array subtypes for buffer option (#​865) (a5231e7)

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

⚠ BREAKING CHANGES
  • refactor v1 internal state and options logic (#​780)
  • refactor v7 internal state and options logic, fixes #​764 (#​779)
  • Port to TypeScript, closes #​762 (#​763)
  • update node support matrix (only support node 16-20) (#​750)
Features
Bug Fixes

v10.0.0

Compare Source

⚠ BREAKING CHANGES
  • update node support (drop node@​12, node@​14, add node@​20) (#​750)
Features
Bug Fixes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/npm-uuid-vulnerability branch 4 times, most recently from be31b09 to d65b841 Compare April 29, 2026 18:53
@renovate renovate Bot force-pushed the renovate/npm-uuid-vulnerability branch 2 times, most recently from 012296b to ff469cc Compare May 4, 2026 20:44
@renovate renovate Bot changed the title Update dependency uuid to v14 [SECURITY] Update dependency uuid to v14 [SECURITY] - abandoned May 5, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 5, 2026

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@renovate renovate Bot force-pushed the renovate/npm-uuid-vulnerability branch from ff469cc to f69288f Compare May 6, 2026 04:54
@renovate renovate Bot changed the title Update dependency uuid to v14 [SECURITY] - abandoned Update dependency uuid to v11 [SECURITY] May 6, 2026
@renovate renovate Bot force-pushed the renovate/npm-uuid-vulnerability branch 12 times, most recently from b201169 to ed1901d Compare May 12, 2026 18:28
@renovate renovate Bot force-pushed the renovate/npm-uuid-vulnerability branch 3 times, most recently from 6d6fae9 to 54092c4 Compare May 18, 2026 20:01
@renovate renovate Bot changed the title Update dependency uuid to v11 [SECURITY] Update dependency uuid to v11 [SECURITY] - autoclosed May 19, 2026
@renovate renovate Bot closed this May 19, 2026
@renovate renovate Bot deleted the renovate/npm-uuid-vulnerability branch May 19, 2026 15:33
@renovate renovate Bot changed the title Update dependency uuid to v11 [SECURITY] - autoclosed Update dependency uuid to v11 [SECURITY] May 21, 2026
@renovate renovate Bot reopened this May 21, 2026
@renovate renovate Bot force-pushed the renovate/npm-uuid-vulnerability branch 2 times, most recently from 54092c4 to 142d654 Compare May 21, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants