CVE-2026-126729: Composer/drupal/auth_login_plus vulnerability

Published Nov 11, 2026
·
Updated

This module enables you to require a second authentication factor (a time-based one-time password from an authenticator app) when users log in.

The module doesn't sufficiently enforce the second factor for authentication providers that authenticate every request on their own. An attacker who knows the password of an account with two-factor authentication enabled can use that account's permissions through routes that accept such a provider, without providing the second factor.

This vulnerability is mitigated by the fact that the attacker must know the account's password, a per-request authentication provider (such as the the HTTP Basic Authentication module) must be enabled, and an alternate authentication method (such as JSON:API or REST) must be enabled.

Affected Software

1 affected componentFixes available
composer/drupal/auth_login_plus<1.0.3
1.0.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/drupal/auth_login_plus to a version that resolves this vulnerability.

    Fixed in 1.0.3

Event History

Nov 11, 2026
Advisory Published
via OSV·05:43 PM
Data Sourced
via OSV·05:43 PM
DescriptionAffected Software

Frequently Asked Questions

1

Which deployments are exposed to this authentication bypass?

Exposure requires all of the following: an account with two-factor authentication enabled, a per-request authentication provider such as the HTTP Basic Authentication module, and an alternate authentication method such as JSON:API or REST. The attacker must also know the affected account's password.

2

What can an attacker do if the issue is exploited?

An attacker can use the permissions of a two-factor-protected account through routes that accept a per-request authentication provider without supplying the required time-based one-time password.

3

What should be reviewed if patching cannot happen immediately?

Review whether per-request authentication providers and alternate authentication methods are enabled, particularly HTTP Basic Authentication together with JSON:API or REST. Reducing or disabling the relevant providers or alternate methods removes conditions identified as necessary for exploitation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203