# CVE-2026-46434: wger: Trainer Privilege Escalation - Improper Privilege Management

> A gym trainer can deactivate higher-privileged manager accounts due to missing hierarchy checks, allowing unauthorized account deactivation.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-x249-cx55-2h87, PYSEC-2026-4316

## What is CVE-2026-46434?

CVE-2026-46434 is a high-severity vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wger is a free, open-source workout and fitness manager. Prior to version 2.6, a user with only the `gym_trainer` permission can deactivate any account in the same gym, including `gym_manager` and `general_gym_manager` accounts. The `UserDeactivateView` grants access to anyone holding any one of `gym.manage_gym`, `gym.manage_gyms`, or `gym.gym_trainer` (OR logic via `WgerMultiplePermissionRequiredMixin`), and performs no privilege-hierarchy check to prevent a lower-privileged role from disabling a higher-privileged one. Version 2.6 fixes the issue.

Weakness: CWE-269 (Improper Privilege Management)

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

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-46434?

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

## Is CVE-2026-46434 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46434 is a high-severity vulnerability in wger-project wger, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46434 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-46434/ (Markdown: https://insights.sbomify.com/CVE-2026-46434/index.md)
```

## Sources

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

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