Quick answers
- Is CVE-2026-107146 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107146 being exploited in the wild.
- How severe is CVE-2026-107146?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Alexandregz Twofactor Gauthenticator before commit 4640889.
- Is there a fix for CVE-2026-107146?
- Yes: fixed in commit 4640889. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107146 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107146?
- Check whether you run Alexandregz Twofactor Gauthenticator 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.
How to fix
- Fixed in: commit 4640889
Technical details
The plugin fails to properly destroy sessions on the server side when two-factor verification fails, allowing attackers to ignore logout redirects and maintain session persistence. An attacker with knowledge of the target user's password can exploit this by keeping a session alive while attempting to brute-force the 6-digit second-factor code, potentially leading to complete account compromise and email access.
Affected products
- alexandregz twofactor_gauthenticator before commit 4640889
Timeline
- 2026-10-27: disclosed
- 2026-10-27: patched: Fixed in commit 4640889