Is CVE-2026-108515 exploited in the wild?

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

How severe is CVE-2026-108515?

Informational severity, published 30 October 2026.

Which products and versions are affected?

Drupal Core 8.9.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=8.9.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-108515?

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-108515 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-108515?

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-108515: Drupal core Link module cross-site scripting in markup sanitization

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

Drupal is a widely-used open-source content management system. The Link module allows websites to store internal and external URLs as field data. Insufficient sanitization of markup can allow attackers to inject malicious scripts that execute in the browsers of site visitors, potentially stealing session tokens, defacing content, or redirecting users to malicious sites.

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

Quick answers

Is CVE-2026-108515 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-108515 being exploited in the wild.
How severe is CVE-2026-108515?: Informational severity, published 30 October 2026.
Which products and versions are affected?: Drupal Core 8.9.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=8.9.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-108515?: 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-108515 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-108515?: 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 Drupal core Link module fails to properly sanitize markup in certain contexts, leading to reflected or stored cross-site scripting (XSS) vulnerabilities. The flaw requires user interaction (such as visiting a page with the malicious content or an authenticated user creating the malicious link field). An attacker with the ability to create or edit link fields can inject HTML/JavaScript that executes in browsers of any user viewing the affected content.

Affected products

Drupal core 8.9.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-108515
DRUPAL-CORE-2026-015

Timeline

2026-10-14: disclosed

References

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