# CVE-2026-15916: Drupal core - Moderately critical - Information disclosure - SA-CORE-2026-010

> Attackers can access unauthorized information due to missing authorization checks in Drupal core, requiring an upgrade to secure the application.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** DRUPAL-CORE-2026-010, GHSA-jw5p-wr38-7rv7

## What is CVE-2026-15916?

CVE-2026-15916 is a medium-severity missing authorization vulnerability in Drupal core, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Missing Authorization vulnerability in Drupal Drupal core allows Forceful Browsing. This issue affects Drupal core versions: from 0.0.0 to 10.6.13, from 11.3.0 to 11.3.14, from 11.4.0 to 11.4.4, from 0.0.0 to 11.0.*, from 0.0.0 to 11.1.*, from 0.0.0 to 11.2.*.

Weakness: CWE-862 (Missing Authorization)

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

1 open source package ship an affected version, including drupal/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/core` | Packagist | All versions | 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0 |

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

Upgrade drupal/core to a fixed version for your release line: 10.6.13, 11.3.14, 11.4.4 or 11.1.0.

## Is CVE-2026-15916 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15916 is a medium-severity missing authorization vulnerability in Drupal core, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-15916 in the wild and no public exploit code.

Affected packages and fixed versions:
- drupal/core (Packagist): affected all versions; fixed in 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0

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-15916/ (Markdown: https://insights.sbomify.com/CVE-2026-15916/index.md)
```

## Sources

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

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