fix(deps): bump nanoid 3.3.17 → 3.3.18 (Dependabot #189) - #200
Merged
Conversation
Resolves Dependabot alert #189 (GHSA-2v37-7h3g-55p8 / CVE-2026-67213). nanoid before 3.3.18 can loop indefinitely when customAlphabet or customRandom is called with size=0, causing a denial-of-service. nanoid is a transitive dependency via postcss in the website/ Docusaurus sub-project; not directly imported in any source file. Updates both the overrides entry and the lockfile resolution.
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
Bumps nanoid from 3.3.17 to 3.3.18 to resolve Dependabot alert #189.
Advisory: GHSA-2v37-7h3g-55p8 / CVE-2026-67213
Severity: HIGH
Issue: nanoid before 3.3.18 can loop indefinitely when
customAlphabetorcustomRandomis called withsize=0, causing a denial-of-service condition.Context
postcssin thewebsite/Docusaurus sub-projectwebsite/src/overridesentry inwebsite/package.jsonwas already pinning nanoid at 3.3.17; this bumps it to the patched 3.3.18npm install --package-lock-only— all nanoid resolutions now point to 3.3.18Changes
website/package.json: overridesnanoid→3.3.18website/package-lock.json: resolved version →3.3.18Verification