This module provides a framework for integrating Drupal with AI providers. Its AI Search submodule provides a Search API backend that stores content in a vector... (CVE-2026-118550)

Package: drupal/ai
Fixed in: 1.4.11, 1.5.2
Published: Wed 28 Oct 2026, 17:09 Lisbon

In plain words

Users can be shown cached search results containing titles and other displayed fields from unpublished or access-restricted content they cannot access. This happens when the AI Search submodule is used with a Search API view using result caching, and an authorised user has run the same search within the cache lifetime. RAG tools, AI Assistant RAG actions and custom code running Search API queries are not affected.

Am I affected?

Look for drupal/ai and its version in composer.lock. The advisory lists fixes in 1.4.11 and 1.5.2 but gives no affected version range. Check whether the AI Search submodule is enabled and used with a Search API view whose result caching is Search API (time-based), Search API (tag-based) or Search API (time and tag-based). Exposure also requires a user with access to restricted content to have run the same search within the cache lifetime.

What to do

Check which version you have, then update to a fixed release for your branch (1.4.11, 1.5.2):

composer show drupal/ai | grep versions
composer update drupal/ai

If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.

If you cannot update yet

Use the default view result caching setting, Search API (none), which is not affected.

The advisory's description

This module provides a framework for integrating Drupal with AI providers. Its AI Search submodule provides a Search API backend that stores content in a vector database for semantic search.

The AI Search submodule has always been marked as 'experimental' but more importantly is deprecated. You may wish to use this as an opportunity to move to the standalone AI Search which is a drop-in replacement and target of all new development. It also had the same vulnerability.

The AI Search backend checks access to each search result for the current user, but this is not taken into account when Search API caches the results of a view. As a result, cached search results, including titles and other displayed fields of unpublished or access-restricted content, can be shown to users who do not have access to that content in some configurations.

This vulnerability is mitigated by the fact that:

The AI Search submodule must be enabled and used with a Search API view.
The view must use Search API result caching ("Search API (time-based)", "Search API (tag-based)" or "Search API (time and tag-based)"). The default, "Search API (none)", is not affected.
A user with access to the restricted content must have run the same search within the cache lifetime.

Retrieval-augmented generation (RAG) tools, AI Assistant RAG actions and custom code running Search API queries are not affected.

The advisory

From OSV.dev, which gathers the GitHub Advisory Database, FriendsOfPHP and Drupal security advisories; the summary is theirs. The description is OSV's record of the advisory. "In plain words", "Am I affected?" and "If you cannot update yet" are based on that advisory, and checked to name no version it does not.