# CVE-2026-96387: Stop administrator login - Moderately critical - Access bypass - SA-CONTRIB-2026-183


- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** DRUPAL-CONTRIB-2026-183, GHSA-q2g9-878h-hxmh

## What is CVE-2026-96387?

CVE-2026-96387 is a low-severity vulnerability in Drupal Stop administrator login, published on 22 Oct 2026. 

### Official description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Stop administrator login allows Authentication Bypass. This issue affects Stop administrator login versions: from 1.0 to 1.6.

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

## Which versions are affected by CVE-2026-96387?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/stop_admin` | Packagist:https://packages.drupal.org/8 | From 1.0.0 | 1.6.0 |

## How do I fix CVE-2026-96387?

Upgrade to a fixed version.

## Is CVE-2026-96387 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96387 and fix it if it is affected.

What it is: CVE-2026-96387 is a low-severity vulnerability in Drupal Stop administrator login, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-96387 in the wild and no public exploit code.

Affected product: Drupal Stop administrator 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-2026-96387/ (Markdown: https://insights.sbomify.com/CVE-2026-96387/index.md)
```

## Sources

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

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