# CVE-2026-1917: Login Disable - Less critical - Access bypass - SA-CONTRIB-2026-008

> Attackers can bypass authentication restrictions in the Drupal Login Disable module, allowing unauthorized access to protected functionality.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** DRUPAL-CONTRIB-2026-008, GHSA-j568-7wm8-fm52

## What is CVE-2026-1917?

CVE-2026-1917 is a medium-severity authentication bypass vulnerability in Drupal Login Disable, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal Login Disable allows Functionality Bypass.This issue affects Login Disable: from 0.0.0 before 2.1.3.

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

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

It affects 1 product.


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

Products: Budda Login Disable.

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

Upgrade to a fixed version.

## Is CVE-2026-1917 being exploited?

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

## Other vulnerabilities in Drupal Login Disable

- [CVE-2026-15079](https://insights.sbomify.com/CVE-2026-15079/): Login Disable - Moderately critical - Access bypass - SA-CONTRIB-2026-070 (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1917 is a medium-severity authentication bypass vulnerability in Drupal Login Disable, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1917 in the wild and no public exploit code.

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

## Sources

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

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