# CVE-2026-82466: Rodauth before 2.46.0 Authentication Bypass via webauthn_login

> Logged-in users can bypass authentication to access any other account due to improper credential binding validation in Rodauth.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-82466, GHSA-3pvr-v35r-4r75, GHSA-qw88-v783-w782, UBUNTU-CVE-2026-82466

## What is CVE-2026-82466?

CVE-2026-82466 is a critical authentication bypass vulnerability in jeremyevans rodauth, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-82466?


## How do I fix CVE-2026-82466?

Upgrade to a fixed version.

## Is CVE-2026-82466 being exploited?

There is no known exploitation of CVE-2026-82466 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82466 and fix it if it is affected.

What it is: CVE-2026-82466 is a critical authentication bypass vulnerability in jeremyevans rodauth, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82466 in the wild and no public exploit code.

Affected product: jeremyevans rodauth. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82466/ (Markdown: https://insights.sbomify.com/CVE-2026-82466/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82466
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82466
- OSV: https://osv.dev/vulnerability/CVE-2026-82466

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82466/
Summaries are generated and may contain mistakes; the official description above is the record.