Quick answers
- Is CVE-2026-107254 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107254 being exploited in the wild.
- How severe is CVE-2026-107254?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal Authenticator Login Plus (2FA) <1.0.1; Packagist:Https://Packages.Drupal.Org/8 Drupal/Auth Login Plus ECOSYSTEM:introduced=0,fixed=1.0.1.
- Is there a fix for CVE-2026-107254?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Auth Login Plus: upgrade to 1.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107254 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107254?
- Check whether you run Drupal Authenticator Login Plus (2FA) or Packagist:Https://Packages.Drupal.Org/8 Drupal/Auth Login Plus 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
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Auth Login Plus: upgrade to 1.0.1 or later
Technical details
The Authenticator Login Plus module does not properly enforce TOTP verification during authentication flows that use Drupal core's one-time login link mechanism. An attacker who obtains a valid one-time login link (e.g., through password reset, email compromise, or social engineering) can use it to log in and bypass the mandatory second factor. The vulnerability affects all versions prior to 1.0.1.
Affected products
- Drupal Authenticator Login Plus (2FA) <1.0.1
Identifiers
- CVE-2026-107254
- DRUPAL-CONTRIB-2026-197
Timeline
- 2026-10-07: disclosed