Quick answers
- Is CVE-2026-118552 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118552 being exploited in the wild.
- How severe is CVE-2026-118552?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal AI <1.4.11, >=1.5.0 <1.5.2; Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai ECOSYSTEM:introduced=0,fixed=1.4.11|ECOSYSTEM:introduced=1.5.0,fixed=1.5.2.
- Is there a fix for CVE-2026-118552?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai: upgrade to 1.4.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118552 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118552?
- Check whether you run Drupal AI or Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai 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
- Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai: upgrade to 1.4.11 or later
Technical details
The module fails to properly sanitize HTMX attributes, allowing stored or reflected cross-site scripting (XSS) attacks. An attacker can inject JavaScript code through unsanitized HTMX attributes that will execute in the context of other users' browsers. This is a client-side vulnerability that requires user interaction to exploit.
Affected products
- Drupal AI <1.4.11, >=1.5.0 <1.5.2
Identifiers
- CVE-2026-118552
- DRUPAL-CONTRIB-2026-272
Timeline
- 2026-10-28: disclosed