Quick answers
- Is CVE-2026-46437 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46437 being exploited in the wild.
- How severe is CVE-2026-46437?
- Medium severity, with a CVSS score of 4.8, published 7 October 2026.
- Which products and versions are affected?
- wger (PyPI) <= 2.1, ECOSYSTEM:introduced=0,last_affected=2.1; Wger all versions.
- Is there a fix for CVE-2026-46437?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-46437 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-46437?
- Check whether you run wger (PyPI) or Wger at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in wger's authentication lifecycle: logout via the `/user/logout` endpoint only clears the Django session cookie and does not revoke DRF authtokens or JWT refresh tokens. Similarly, password changes do not invalidate existing API credentials—DRF tokens remain in the database unchanged, and JWT refresh tokens lack server-side revocation. An attacker with a stolen bearer token can continue to access protected `/api/v2/*` endpoints and refresh access tokens until token expiry or manual rotation.
Affected products
- wger wger all versions
Identifiers
- CVE-2026-46437
- GHSA-v3x9-6gg8-c2c9
- PYSEC-2026-4315
Timeline
- 2026-10-07: disclosed