# The Navigation module doesn't sufficiently sanitize certain attributes, which can lead to a cross-site scripting (XSS) vulnerability.

Advisory record · `DRUPAL-CORE-2026-016`

- **Identifiers:** `DRUPAL-CORE-2026-016` · `CVE-2026-108514`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 14 Oct 2026
- **Updated:** 17 Oct 2026
- **Reviewed by a person:** No

Published by OSV at 14 Oct 2026, 17:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `drupal/core` (Packagist): affected `>=10.3.0, <10.6.19 || >=11.0.0, <11.3.19 || >=11.4.0, <11.4.10 || >=12.0.0-alpha1, <12.0.0-beta2`; fixed in `10.6.19`, `11.3.19`, `11.4.10`, `12.0.0-beta2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Navigation module in Drupal core (drupal/core on Packagist) is affected in versions from 10.3.0 before 10.6.19, from 11.0.0 before 11.3.19, from 11.4.0 before 11.4.10, and from 12.0.0-alpha1 before 12.0.0-beta2. An attacker would need an account with a role that can enter HTML tags with specific data attributes, or with the administer menu permission, and could then use the insufficient sanitization to run cross-site scripting. The fix is to upgrade drupal/core to 10.6.19, 11.3.19, 11.4.10, or 12.0.0-beta2, depending on the release line in use.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 11th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 30 Oct 2026, 03:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-108514)
- 30 Oct 2026, 04:18 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-108514)
- 31 Oct 2026, 13:53 UTC: First seen by agentprime
- 31 Oct 2026, 13:53 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/DRUPAL-CORE-2026-016)

## Sources

- [OSV: DRUPAL-CORE-2026-016](https://osv.dev/vulnerability/DRUPAL-CORE-2026-016)
- <https://www.drupal.org/sa-core-2026-016>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/DRUPAL-CORE-2026-016>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/DRUPAL-CORE-2026-016/>. Everything for agents: <https://agentprime.io/llms.txt>.