# CVE-2026-82466: Rodauth authentication bypass in webauthn_login

Source: https://junglewise.ai/threats/cve-2026-82466-rodauth-authentication-bypass-in-webauthn-login  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-29. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-82466 · Severity: high · CVSS 8.7 · Published 2026-08-29

Rodauth is a Ruby authentication framework used to secure user login for web applications. A flaw in the WebAuthn login feature allows attackers who are already logged in as one user to impersonate any other account without validating proper credential ownership, enabling account takeover and unauthorized access to other users' data.

Technologies: [Jeremy Evans Rodauth](https://junglewise.ai/threats/technologies/rodauth). Vendors: [Jeremy Evans](https://junglewise.ai/threats/vendors/jeremy-evans).

## Quick answers

**Is CVE-2026-82466 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-82466 being exploited in the wild.

**How severe is CVE-2026-82466?** High severity, with a CVSS score of 8.7, published 29 August 2026.

**Which products and versions are affected?** Jeremy Evans Rodauth before 2.46.0.

**Is there a fix for CVE-2026-82466?** A patch was published on 2026-08-18: Security fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-82466 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-82466?** Check whether you run Jeremy Evans Rodauth at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an authentication bypass in the webauthn_login route caused by improper account resolution logic. When a user is already logged in, the authentication handler falls back to using session-based account identifiers instead of validating that the WebAuthn credential is properly bound to the target account. An attacker with an active session can exploit this to authenticate as any arbitrary account, whether or not that account has WebAuthn enabled. The flaw affects Rodauth versions prior to 2.46.0 and was fixed by enforcing credential-to-account binding validation. Exploitation requires an active authenticated session.

## Affected products

- Jeremy Evans Rodauth before 2.46.0

## Timeline

- 2026-08-29: disclosed
- 2026-08-18: patched: Security fix committed to repository

## References

- [https://github.com/jeremyevans/rodauth](https://github.com/jeremyevans/rodauth)
- [https://github.com/jeremyevans/rodauth/commit/35d74a9f07b2005a8ea75fc11a6539c04f3c2840](https://github.com/jeremyevans/rodauth/commit/35d74a9f07b2005a8ea75fc11a6539c04f3c2840)

## Related threats

- [Rodauth TOTP code reuse vulnerability in OTP feature](https://junglewise.ai/threats/cve-2026-82470-rodauth-totp-code-reuse-vulnerability-in-otp-feature)
- [Rodauth JWT refresh authentication bypass in non-POST requests](https://junglewise.ai/threats/cve-2026-82469-rodauth-jwt-refresh-authentication-bypass-in-non-post-requests)
- [Rodauth CSRF protection bypass in JSON request validation](https://junglewise.ai/threats/cve-2026-82468-rodauth-csrf-protection-bypass-in-json-request-validation)