Quick answers
- Is CVE-2026-118548 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118548 being exploited in the wild.
- How severe is CVE-2026-118548?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Drupal AI <1.4.11 or >=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-118548?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai: upgrade to 1.4.11 or later. Until then: Avoid using the AI module with untrusted data sources that produce rendered HTML output until patching is complete. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118548 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118548?
- 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
Avoid using the AI module with untrusted data sources that produce rendered HTML output until patching is complete.
Technical details
The AI module fails to properly validate hyperlinks when processing HTML output under specific conditions, enabling information exfiltration via links to attacker-controlled external sites. This is a client-side or server-side rendering vulnerability in link sanitization logic. Exploitation requires an attacker to inject malicious content through untrusted data sources that the module then renders as HTML output.
Affected products
- Drupal AI <1.4.11 or >=1.5.0 <1.5.2
Identifiers
- CVE-2026-118548
- DRUPAL-CONTRIB-2026-268
Timeline
- 2026-10-28: disclosed