Quick answers
- Is CVE-2026-107145 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107145 being exploited in the wild.
- How severe is CVE-2026-107145?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Alexandregz Twofactor Gauthenticator all before commit 4640889.
- Is there a fix for CVE-2026-107145?
- 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-107145 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107145?
- 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 vulnerability is a lack of rate limiting (CWE-307) in the second-factor authentication code validation mechanism. An authenticated attacker can submit arbitrary 6-digit codes without restriction, allowing brute-force attacks with reasonable probability of success within the typical time window a code is valid. Related vulnerabilities in the same plugin include session persistence after failed 2FA verification (CVE-2026-107146) and IP spoofing in 2FA bypass (CVE-2026-107147).
Affected products
- alexandregz twofactor_gauthenticator all before commit 4640889
Timeline
- 2026-10-27: disclosed