Predictable results in nanoid generation when given non-integer values

Description

When nanoid is called with a fractional value, there were a number of undesirable effects:

1. in browser and non-secure, the code infinite loops on while (size–)
2. in node, the value of poolOffset becomes fractional, causing calls to nanoid to return zeroes until the pool is next filled 3.

Recommendation

Update the nanoid package to the latest compatible version. Followings are version details:

• Affected version(s): **< 3.3.8

  >= 4.0.0, < 5.0.9**

• Patched version(s): **3.3.8

  5.0.9**

References

• GHSA-mwcw-c2x4-8c55
• lists.debian.org
• CVE-2024-55565
• CWE-835
• CAPEC-310
• OWASP 2021-A6

Related Issues

• Exposure of Sensitive Information to an Unauthorized Actor in nanoid - CVE-2021-23566
• OpenList (frontend) allows XSS Attacks in the built-in Markdown Viewer - CVE-2025-50183
• tarteaucitron.js allows UI manipulation via unrestricted CSS injection - CVE-2025-31138
• Potential DoS when using ContextLines integration (GHSA-r5w7-f542-q2j4) - Vulnerability

Tags:

npm

nanoid