# CVE-2026-82469: Rodauth before 2.47.0 Authentication Bypass via jwt_refresh

> Attackers can bypass authentication in Rodauth by exploiting the jwt_refresh route to obtain new access tokens, leading to indefinite account access.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-82469, GHSA-mhhp-hxcr-939w, GHSA-w4fg-qf56-62m2, UBUNTU-CVE-2026-82469

## What is CVE-2026-82469?

CVE-2026-82469 is a medium-severity authentication bypass vulnerability in jeremyevans rodauth, published on 29 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Rodauth before 2.47.0 contains an authentication bypass vulnerability in the jwt_refresh route that issues new JWT access tokens without requiring a refresh token. Attackers can present an access token to the refresh route via non-POST methods to obtain a new valid access token, enabling indefinite account access with temporary token possession.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

Upgrade to a fixed version.

## Is CVE-2026-82469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82469 is a medium-severity authentication bypass vulnerability in jeremyevans rodauth, published on 29 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82469 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-82469/ (Markdown: https://insights.sbomify.com/CVE-2026-82469/index.md)
```

## Sources

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

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