CVE-2026-46437: wger · Improper Authentication
Affects wgerSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.6 when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Upgrade wger and wger-project/wger to 2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wger-projectwger | Affected
| Fixed in
|
GitHubwger-project/wgerpkg:github/wger-project/wgerOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to wger version 2.6 or later, which contains the official fix for this improper authentication vulnerability. Until upgrading, tokens remain valid after logout or password change, so manual token rotation or revocation is necessary to mitigate risk. There is no indication that other mitigations fully address this issue.
Description
wger versions prior to 2.6 contain an improper authentication vulnerability where bearer-style API tokens remain valid after user logout or password change. This allows an attacker with a stolen token to continue accessing protected API endpoints until the token expires or is manually revoked. Version 2.6 includes a patch to address this issue.