# CVE-2026-11915: Brute force attack protection - Critical - Unsupported - SA-CONTRIB-2026-047

> The Drupal Brute Force Attack Protection module is unsupported, leaving sites vulnerable to brute force attacks due to lack of maintenance.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** DRUPAL-CONTRIB-2026-047, GHSA-q4vw-q8jq-2jg7

## What is CVE-2026-11915?

CVE-2026-11915 is a medium-severity vulnerability in Drupal Brute force attack protection, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

vulnerability in Drupal Brute force attack protection allows . This issue affects Brute force attack protection versions: *.*.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

No fix has been published for CVE-2026-11915 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11915 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11915 is a medium-severity vulnerability in Drupal Brute force attack protection, published on 10 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11915 in the wild and no public exploit code.

Affected product: Drupal Brute force attack protection. 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-11915/ (Markdown: https://insights.sbomify.com/CVE-2026-11915/index.md)
```

## Sources

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

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