Quick answers
- Is CVE-2026-84911 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84911 being exploited in the wild.
- How severe is CVE-2026-84911?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Drupal AI < 1.3.13, >= 1.4.0 < 1.4.8; Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai ECOSYSTEM:introduced=0,fixed=1.3.13|ECOSYSTEM:introduced=1.4.0,fixed=1.4.8.
- Is there a fix for CVE-2026-84911?
- Yes. Packagist:Https://Packages.Drupal.Org/8 Drupal/Ai: upgrade to 1.3.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84911 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84911?
- 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.3.13 or later
Technical details
The vulnerability is an insufficient input sanitization flaw in the structured results processing of legacy agent setups, allowing reflected or stored XSS via prompt injection. Attack requires both editorial content creation privileges and the presence of AI module versions prior to 1.3.13 or 1.4.0–1.4.7 configured with the legacy 1.0.x agent branch in a non-standard setup. Patched versions (1.3.13 and 1.4.8+) have been released and eliminate the vulnerability.
Affected products
- Drupal AI < 1.3.13, >= 1.4.0 < 1.4.8
Identifiers
- CVE-2026-84911
- DRUPAL-CONTRIB-2026-119
Timeline
- 2026-09-02: disclosed