wger has an Uncontrolled Resource Consumption issue

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-86255: 0.44% estimated exploitation activity in the next 30 days; percentile 37.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Any authenticated user can create a routine spanning an arbitrarily long date range (e.g. 100 years) and then trigger the datesequence computation via any of the routine detail endpoints. The server iterates once per day in an unbounded while loop with no maximum duration validation, causing a single HTTP request to consume multiple seconds of server CPU and return a response containing tens of thousands of entries. Repeated requests can exhaust all worker threads and deny service to other users. Details The Routine model (file: wger/manager/models/routine.py) has start and end date fields with only one validation -- start must not be after end: The RoutineSerializer (file: wger/manager/api/serializers.py, line 43) likewise performs no validation on the delta between start and end. The datesequence property (line 256) uses an unbounded loop: A routine with start=2000-01-01 and end=2099-12-31 produces 36,525 iterations, each performing O(slots x entries x configs) work. Five…

Published by the source

13 May 2026, 15:33 UTC

Last modified by the source

10 Sep 2026, 03:50 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v25j-wqcw-fvhj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v25j-wqcw-fvhj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-86255

Advisory: wger has an Uncontrolled Resource Consumption issue
IDs: CVE-2026-86255, GHSA-v25j-wqcw-fvhj
Record: https://patchnext.com/advisories/cve-2026-86255 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI wger: affected <= 2.5

## Suggested inspection (read-only)
- `python -m pip show wger`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wger.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v25j-wqcw-fvhj (OSV record GHSA-v25j-wqcw-fvhj lists affected ranges: PyPI wger >=0 <=2.5)
- Verified: https://github.com/advisories/GHSA-v25j-wqcw-fvhj (GitHub-reviewed advisory GHSA-v25j-wqcw-fvhj lists affected ranges: PyPI wger >=0 <=2.5)

Commands are suggestions: review each one before running it.