# CVE-2025-8093: Authenticator Login - Moderately critical - Access bypass - SA-CONTRIB-2025-098


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Oct 2025
- **Updated:** 15 Oct 2025
- **Also known as:** DRUPAL-CONTRIB-2025-098, GHSA-pjrr-5qr2-gxw3

## What is CVE-2025-8093?

CVE-2025-8093 is a high-severity vulnerability in Drupal Authenticator Login, published on 10 Oct 2025. 

### Official 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.8.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-8093?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/alogin` | Packagist:https://packages.drupal.org/8 | All versions | 2.1.8 |

Products: Authenticator Login Project Authenticator Login.

## How do I fix CVE-2025-8093?

Upgrade to a fixed version.

## Is CVE-2025-8093 being exploited?

There is no known exploitation of CVE-2025-8093 in the wild and no public exploit code.

## Other vulnerabilities in Drupal Authenticator Login

- [CVE-2025-8995](https://insights.sbomify.com/CVE-2025-8995/): Authenticator Login - Highly critical - Access bypass - SA-CONTRIB-2025-096 (critical 9.8)
- [CVE-2025-31681](https://insights.sbomify.com/CVE-2025-31681/): Authenticator Login - Critical - Access bypass - SA-CONTRIB-2025-009 (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8093 and fix it if it is affected.

What it is: CVE-2025-8093 is a high-severity vulnerability in Drupal Authenticator Login, published on 10 Oct 2025. 
Exploitation: There is no known exploitation of CVE-2025-8093 in the wild and no public exploit code.

Affected product: Drupal Authenticator Login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8093/ (Markdown: https://insights.sbomify.com/CVE-2025-8093/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8093
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8093
- OSV: https://osv.dev/vulnerability/CVE-2025-8093

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8093/
Summaries are generated and may contain mistakes; the official description above is the record.