CVE-2025-8995: Drupal Authenticator Login · Authentication Bypass Using an Alternate Path or Channel
Affects Drupal Authenticator LoginSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Drupal Authenticator Login | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-8995, organizations should immediately upgrade the Drupal Authenticator Login module to version 2.1.4 or later once it becomes available. Until an official patch is released, consider implementing the following specific measures: 1) Restrict network access to the authentication endpoints using firewall rules or web application firewalls (WAF) to limit exposure to trusted IPs only. 2) Enable multi-factor authentication (MFA) at the Drupal application level to add an additional layer of verification beyond the vulnerable module. 3) Monitor authentication logs closely for unusual login attempts or patterns indicative of bypass attempts. 4) Conduct a thorough audit of user accounts and permissions to minimize the impact of potential unauthorized access. 5) Temporarily disable or replace the Authenticator Login module with alternative, secure authentication mechanisms if feasible. 6) Keep Drupal core and all modules up to date to reduce the attack surface. 7) Employ intrusion detection and prevention systems (IDS/IPS) to detect anomalous traffic targeting authentication paths. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and layered defenses specific to the nature of this authentication bypass vulnerability.
Description
Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Authenticator Login allows Authentication Bypass.This issue affects Authenticator Login: from 0.0.0 before 2.1.4.