Skip to content

fix: upgrade nanoid to 3.3.17, 5.1.6 (CVE-2026-67213) - #104

Merged
sajeetharan merged 1 commit into
sajeetharan:mainfrom
anupamme:fix-repo-devglobe-cve-2026-67213-nanoid
Aug 11, 2026
Merged

fix: upgrade nanoid to 3.3.17, 5.1.6 (CVE-2026-67213)#104
sajeetharan merged 1 commit into
sajeetharan:mainfrom
anupamme:fix-repo-devglobe-cve-2026-67213-nanoid

Conversation

@anupamme

Copy link
Copy Markdown
Contributor

Summary

Upgrade nanoid from 3.3.16 to 3.3.17, 5.1.6 to fix CVE-2026-67213.

Vulnerability

Field Value
ID CVE-2026-67213
Severity HIGH
Scanner trivy
Rule CVE-2026-67213
File package-lock.json (dependency: nanoid)
Assessment Present in dependency tree, not confirmed reachable

Description: nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customA ...

Evidence

Scanner confirmation: trivy rule CVE-2026-67213 flagged this pattern.

Changes

  • package.json
  • package-lock.json

Behavior Preservation

The change is scoped to 2 files on the vulnerable path; it only tightens handling of untrusted input and leaves valid inputs unaffected.


This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.


Automated security fix by OrbisAI Security

Automated dependency upgrade by OrbisAI Security
@vercel

vercel Bot commented Aug 11, 2026

Copy link
Copy Markdown

@anupamme is attempting to deploy a commit to the sajeetharan's projects Team on Vercel.

A member of the Team first needs to authorize it.

@sajeetharan
sajeetharan merged commit 6fb6f0e into sajeetharan:main Aug 11, 2026
1 of 2 checks passed
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.

2 participants