Insufficient Session Expiration Affecting wger package, versions [0,]
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-WGER-21693641
- published24 Oct 2026
- disclosed7 Oct 2026
- creditUnknown
Introduced: 7 Oct 2026
NewCVE-2026-46437 (opens in a new tab)How to fix?
A fix was pushed into the master branch but not yet published.
Overview
Affected versions of this package are vulnerable to Insufficient Session Expiration via the authentication lifecycle in wger/core/views/user.py and the API token management in wger/utils/api_token.py, where bearer-style API credentials are not revoked on logout or password change. The logout handler (/user/logout) calls django_logout(), which clears only the Django session cookie and leaves DRF authtokens and JWT refresh tokens fully intact. An attacker who obtains a victim's Authorization: Token credential or JWT refresh token can continue to call protected /api/v2/* endpoints - reading and mutating the victim's data - until the DRF token is manually deleted or the JWT refresh token naturally expires, regardless of any logout or password change performed by the victim.