Is CVE-2026-108514 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-108514 being exploited in the wild.

How severe is CVE-2026-108514?

Informational severity, published 30 October 2026.

Which products and versions are affected?

Drupal Core 10.3.0 through 10.6.18, 11.0.0 through 11.3.18, 11.4.0 through 11.4.9, 12.0.0-alpha1 through 12.0.0-beta1; drupal/core (Packagist) ECOSYSTEM:introduced=10.3.0,fixed=10.6.19|ECOSYSTEM:introduced=11.0.0,fixed=11.3.19|ECOSYSTEM:introduced=11.4.0,fixed=11.4.10|ECOSYSTEM:introduced=12.0.0-alpha1,fixed=12.0.0-beta2.

Is there a fix for CVE-2026-108514?

Yes. drupal/core (Packagist): upgrade to 10.6.19 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-108514 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-108514?

Check whether you run Drupal Core or drupal/core (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-108514: Drupal Navigation module cross-site scripting in attributes

CVE-2026-108514 · Severity: info · Published 2026-10-30

Drupal's Navigation module, a core content management system component, fails to properly sanitize certain HTML attributes in menu items, allowing attackers to inject malicious scripts. An attacker must have permission to edit HTML tags with specific data attributes or administer menus to exploit this. Successful exploitation could result in script execution within the context of an administrator or other authorized user's browser session.

Technologies: Drupal Core, drupal/core (Packagist). Vendors: Drupal, Packagist.

Quick answers

Is CVE-2026-108514 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-108514 being exploited in the wild.
How severe is CVE-2026-108514?: Informational severity, published 30 October 2026.
Which products and versions are affected?: Drupal Core 10.3.0 through 10.6.18, 11.0.0 through 11.3.18, 11.4.0 through 11.4.9, 12.0.0-alpha1 through 12.0.0-beta1; drupal/core (Packagist) ECOSYSTEM:introduced=10.3.0,fixed=10.6.19|ECOSYSTEM:introduced=11.0.0,fixed=11.3.19|ECOSYSTEM:introduced=11.4.0,fixed=11.4.10|ECOSYSTEM:introduced=12.0.0-alpha1,fixed=12.0.0-beta2.
Is there a fix for CVE-2026-108514?: Yes. drupal/core (Packagist): upgrade to 10.6.19 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-108514 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-108514?: Check whether you run Drupal Core or drupal/core (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

drupal/core (Packagist): upgrade to 10.6.19 or later
```
composer require drupal/core:^10.6.19
```

Technical details

The Navigation module does not sufficiently sanitize data attributes in HTML tags, creating a stored XSS vulnerability. Exploitation requires the attacker to have a role with permission to enter HTML tags containing specific data attributes, or the administer menu permission, making this a privilege-escalation scenario. The vulnerability affects Drupal core versions 10.3.0–10.6.18, 11.0.0–11.3.18, 11.4.0–11.4.9, and 12.0.0-alpha1–12.0.0-beta1.

Affected products

Drupal core 10.3.0 through 10.6.18, 11.0.0 through 11.3.18, 11.4.0 through 11.4.9, 12.0.0-alpha1 through 12.0.0-beta1

Identifiers

CVE-2026-108514
DRUPAL-CORE-2026-016

Timeline

2026-10-14: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.