# CVE-2026-86255: wger before 2.5 Uncontrolled Resource Consumption via date_sequence

> Authenticated attackers can cause denial of service in wger by creating routines with excessively long date ranges, exhausting server resources.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA: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:** 6 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-v25j-wqcw-fvhj, GHSA-vh7q-hj8h-q34m

## What is CVE-2026-86255?

CVE-2026-86255 is a high-severity denial of service vulnerability in wger-project wger, published on 6 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

wger before 2.5 fails to validate the maximum duration of routine date ranges, allowing authenticated users to create routines spanning arbitrarily long periods. Attackers can trigger the date_sequence computation via routine detail endpoints, forcing the server to iterate thousands of times per request and exhaust worker threads, denying service to legitimate users.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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


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

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

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

## Is CVE-2026-86255 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86255 is a high-severity denial of service vulnerability in wger-project wger, published on 6 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86255 in the wild and no public exploit code.

Affected packages and fixed versions:
- wger (PyPI): affected all versions up to 2.5; no fix listed
- wger (PyPI): affected all versions up to 2.5; 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-86255/ (Markdown: https://insights.sbomify.com/CVE-2026-86255/index.md)
```

## Sources

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

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