Skip to content

chore: bump nanoid override to patch CVE-2026-67213 (GHSA-2v37-7h3g-55p8) - #871

Merged
isaque-bock-azion merged 1 commit into
mainfrom
chore/bump-nanoid-cve-2026-67213
Aug 10, 2026
Merged

chore: bump nanoid override to patch CVE-2026-67213 (GHSA-2v37-7h3g-55p8)#871
isaque-bock-azion merged 1 commit into
mainfrom
chore/bump-nanoid-cve-2026-67213

Conversation

@isaque-bock-azion

Copy link
Copy Markdown
Contributor

What

pnpm audit started failing the Security Scans job repo-wide (e.g. on #849): nanoid < 3.3.17GHSA-2v37-7h3g-55p8 (CVE-2026-67213, high — custom generators can loop indefinitely when size is 0). The tree resolves a single copy, nanoid@3.3.16 (~100 transitive paths via postcss).

Fix

Same pattern as the js-yaml bump (#867): a bounded override in pnpm-workspace.yaml

"nanoid@3": ">=3.3.17 <4"

bounded to 3.x (CJS) since postcss pins ^3 and 4.x+ is ESM-only. The 5.x range of the advisory (patched 5.1.6) is not in the tree, so no override for it — keeping the file's minimal-set policy.

Lockfile regenerated (nanoid 3.3.16 → 3.3.18); pnpm audit is clean locally.

@isaque-bock-azion
isaque-bock-azion merged commit 316986f into main Aug 10, 2026
18 checks passed
@isaque-bock-azion
isaque-bock-azion deleted the chore/bump-nanoid-cve-2026-67213 branch August 10, 2026 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants