Thread hang via zero-size custom generator
Published Jul 29, 2026 · Updated Jul 29, 2026
Infinite-loop denial of service in Nano ID before 5.1.6 allows remote attackers to hang a calling thread through a zero size. The customRandom generator accepts size 0, initializes an empty ID, and repeatedly requests random bytes because the unconditional loop cannot reach its return condition. Exposure requires an application to pass an unvalidated attacker-controlled size to customRandom or the customAlphabet wrapper, and the resulting spin interrupts that thread.
Summary
What happened
Infinite-loop denial of service in Nano ID before 5.1.6 allows remote attackers to hang a calling thread through a zero size. The customRandom generator accepts size 0, initializes an empty ID, and repeatedly requests random bytes because the unconditional loop cannot reach its return condition. Exposure requires an application to pass an unvalidated attacker-controlled size to customRandom or the customAlphabet wrapper, and the resulting spin interrupts that thread.
The record
- CVE
- CVE-2026-67213
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- Nano ID Project
- Product
- Nano ID
- Classifications
- CWE-835, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.1.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo