chore(deps): updated nanoid - #226
Merged
Merged
Conversation
SB-virendrasolanke
requested review from
SB-ChetanKorde and
pareshb3089
and
a lite review from Copilot
September 2, 2026 01:39
pareshb3089
approved these changes
Sep 2, 2026
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
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.
Fix high-severity DoS vulnerability in nanoid (CVE-2026-67213)
Summary
Pins the transitive nanoid dependency to ^3.3.18 via a resolutions entry to remediate CVE-2026-67213 (GHSA-2v37-7h3g-55p8).
Vulnerability details
Package: nanoid
Affected version: 3.3.16 (transitive, via postcss)
Patched version: 3.3.18
CVE: CVE-2026-67213
Severity: High (CVSS 8.2)
CWE-835: Loop with Unreachable Exit Condition (Infinite Loop)
customAlphabet and customRandom in affected nanoid versions enter an infinite loop when called with size = 0. Any code path that passes an unvalidated, attacker-controlled size of 0 to these functions hangs the calling thread, resulting in a denial-of-service condition.
Changes
package.json: added "nanoid": "^3.3.18" under resolutions to force all transitive consumers (currently pulled in via postcss) onto the patched version.
yarn.lock: regenerated via yarn install so nanoid now resolves to 3.3.18 instead of 3.3.16.
Verification
Confirmed yarn.lock now contains a single merged entry:
Risk / impact
nanoid is not used directly by this library; it's only a transitive dependency of postcss. The version bump (3.3.16 → 3.3.18) is a patch-level change with no known breaking API changes.
No application code changes required.