fix(deps): bump nanoid to patch CVE-2026-67213 (GHSA-2v37-7h3g-55p8) - #66
Open
svector (Svector-anu) wants to merge 1 commit into
Open
Conversation
Advisory: GHSA-2v37-7h3g-55p8 Severity: high Fixed in: nanoid@3.3.18 Detected by osv-scanner. Transitive via vite -> postcss ^8.5.17 -> nanoid ^3.3.16 (devDependency only, build tooling, not shipped in the app). postcss@8.5.25 already declares nanoid "^3.3.16", so 3.3.18 resolves within its existing declared range — no manifest changes needed, lockfile only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nanoid@3.3.16(transitive dependency ofpostcss, pulled in viavite— devDependency, build-time only) is affected by GHSA-2v37-7h3g-55p8 / CVE-2026-67213: custom generators can loop indefinitely whensizeis zero. Fixed upstream innanoid@3.3.18.Fix
Lockfile-only bump of the transitive
nanoidresolution to3.3.18.postcss@8.5.25(the direct consumer) already declares"nanoid": "^3.3.16", so3.3.18resolves cleanly within its existing declared range — nopackage.jsonchanges needed."node_modules/nanoid": { - "version": "3.3.16", + "version": "3.3.18",Verification
osv-scanner --recursive .before/afternanoid@3.3.16flagged for GHSA-2v37-7h3g-55p8osv-scannerreports zero nanoid findingsvitebuild tooling), not present in shipped app bundlesDetected by
osv-scanner (dependency vulnerability scan).