# CVE-2026-82468: Rodauth before 2.47.0 CSRF Protection Bypass via Content-Type

> Attackers can bypass CSRF protection in Rodauth to force victims to authenticate to attacker-controlled accounts via crafted JSON requests.

- **Severity:** Medium 4.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-82468, GHSA-8928-x2p4-43mr, GHSA-hh2f-xw94-5p79, UBUNTU-CVE-2026-82468

## What is CVE-2026-82468?

CVE-2026-82468 is a medium-severity vulnerability in jeremyevans rodauth, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Rodauth before 2.47.0 contains a cross-site request forgery protection bypass vulnerability in the JSON request content type validation. Attackers can craft cross-origin form posts with content types containing application/json substrings to bypass CSRF token validation and force victims to authenticate to attacker-controlled accounts.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

Upgrade to a fixed version.

## Is CVE-2026-82468 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82468 is a medium-severity vulnerability in jeremyevans rodauth, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82468 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-82468/ (Markdown: https://insights.sbomify.com/CVE-2026-82468/index.md)
```

## Sources

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

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