Rodauth before 2.46.0 contains an authentication bypass vulnerability in the webauthn_login route that allows logged-in users to authenticate as any other account. Attackers can exploit improper account resolution logic that falls back to session account identifiers instead of validating the credential binding to complete authentication as arbitrary users.
CVE-2026-82466
Score 8.7 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. a secondary CVSS source baseline 8.7; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 29, 2026
Advisory Details (4)
Auto-updated Aug 29, 2026Rodauth before 2.46.0 Authentication Bypass via webauthn_login | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rodauth-before-2.46.0-authentication-bypass-via-webauthn-loginGitHub - jeremyevans/rodauth: Ruby's Most Advanced Authentication Framework · GitHub
https://github.com/jeremyevans/rodauthAccount takeover in webauthn_login feature · Advisory · jeremyevans/rodauth · GitHub
https://github.com/jeremyevans/rodauth/security/advisories/GHSA-3pvr-v35r-4r75commit 35d74a9f07b2 (jeremyevans/rodauth)
Fix landed in jeremyevans/rodauth commit 35d74a9f07b2 — awaiting tagged release
https://github.com/jeremyevans/rodauth/commit/35d74a9f07b2005a8ea75fc11a6539c04f3c2840Vendor Advisories for CVE-2026-82466(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 05:07 UTCEG score recompute
- 2026-08-30 05:07 UTCGHSA enrichment
- 2026-08-29 17:28 UTCEG score recompute
- 2026-08-29 16:41 UTCEG score recompute
- 2026-08-29 16:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(4)
What is CVE-2026-82466?
When was CVE-2026-82466 disclosed?
What is the CVSS score of CVE-2026-82466?
How do I remediate CVE-2026-82466?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82466
Is Your Infrastructure Affected by CVE-2026-82466?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.