# CVE-2026-46437: wger: API credentials remain valid after logout/password change

> Attackers with stolen API tokens retain access after logout or password change, allowing unauthorized data access in wger fitness manager.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-v3x9-6gg8-c2c9, PYSEC-2026-4315

## What is CVE-2026-46437?

CVE-2026-46437 is a medium-severity authentication bypass vulnerability in wger-project wger, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wger is a free, open-source workout and fitness manager. Versions prior to 2.6 have a vulnerability in the authentication/session lifecycle of `wger` where bearer-style API credentials remain valid after a user logs out and after a user changes their password. An attacker who steals a victim’s DRF authtoken (`Authorization: Token ...`) or JWT refresh token can continue to access protected `/api/v2/*` endpoints until the token is manually rotated/deleted (DRF token) or naturally expires (JWT refresh). Version 2.6 contains a patch.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-287 (Improper Authentication)

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

3 open source packages ship an affected version, including wger.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |
| `wger` | PyPI | All versions to 2.1 | None |

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

No fix has been published for CVE-2026-46437 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46437 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46437 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46437 is a medium-severity authentication bypass vulnerability in wger-project wger, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46437 exists.

Affected packages and fixed versions:
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed
- wger (PyPI): affected all versions up to 2.1; no fix listed

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-46437/ (Markdown: https://insights.sbomify.com/CVE-2026-46437/index.md)
```

## Sources

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

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