CVE-2026-118550: drupal/ai · This module provides a framework for integrating Drupal with AI providers
Affects drupal/aiSource GCVE Database
Not known to be exploited : upgrade to 1.5.2 or 1.4.11 when convenient.
Data as of 28 Oct 2026, 20:43 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.5.2, 1.4.11
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade drupal/ai to 1.5.2 or 1.4.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/ai | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Drupal AI module versions 1.4.11 or 1.5.2 or later, where this vulnerability is fixed. If upgrading is not immediately possible, avoid enabling Search API result caching with the AI Search submodule. Consider migrating to the standalone AI Search module, which also addresses this issue. No additional action is required if Search API caching is not used.
Description
The Drupal AI module's AI Search submodule has a vulnerability where cached search results may expose titles and fields of unpublished or access-restricted content to unauthorized users under certain configurations. This occurs because the Search API caches results without considering access restrictions, potentially leaking sensitive content. The vulnerability only affects setups using the AI Search submodule with Search API result caching enabled and requires that a user with access to restricted content has previously run the same search within the cache lifetime. Retrieval-augmented generation tools and custom Search API queries are not affected. Fixed versions 1.4.11 and 1.5.2 address this issue.