Authentication Bypass in otpauthGHSA-rmmc-8cqj-hfp3
GHSA-rmmc-8cqj-hfp3 is a security vulnerability in otpauth. A fix is available for otpauth — see the affected versions and patch details below.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
otpauthnpmDescription
Versions of otpauth prior to 3.2.8 are vulnerable to Authentication Bypass. The package's totp.validate() function may return positive values for single digit tokens even if they are invalid. This may allow attackers to bypass the OTP authentication by providing single digit tokens.
Recommendation
Upgrade to version 3.2.8 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | otpauth | all versions | 3.2.8npm install otpauth@3.2.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for otpauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update otpauth to 3.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rmmc-8cqj-hfp3 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-rmmc-8cqj-hfp3 in your dependencies?
Find it across npm, including transitive dependencies.