<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:40:42 +0000</lastBuildDate>
    <item>
      <title>DRUPAL-CONTRIB-2026-270</title>
      <link>https://db.gcve.eu/vuln/drupal-contrib-2026-270</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist:https://packages.drupal.org/8: drupal/ai&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The AI Search submodule has always been marked as &amp;#39;experimental&amp;#39; but more importantly is deprecated. You may wish to use this as an opportunity to move to the standalone [AI Search](https://www.drupal.org/project/ai_search) which is a drop-in replacement and target of all new development. It also had the same vulnerability.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This vulnerability is mitigated by the fact that:&lt;/p&gt;
&lt;p&gt;* The AI Search submodule must be enabled and used with a Search API view.
* The view must use Search API result caching (&amp;#34;Search API (time-based)&amp;#34;, &amp;#34;Search API (tag-based)&amp;#34; or &amp;#34;Search API (time and tag-based)&amp;#34;). The default, &amp;#34;Search API (none)&amp;#34;, is not affected.
* A user with access to the restricted content must have run the same search within the cache lifetime.&lt;/p&gt;
&lt;p&gt;Retrieval-augmented generation (RAG) tools, AI Assistant RAG actions and custom code running Search API queries are not affected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist:https://packages.drupal.org/8: drupal/ai&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The AI Search submodule has always been marked as &amp;#39;experimental&amp;#39; but more importantly is deprecated. You may wish to use this as an opportunity to move to the standalone [AI Search](https://www.drupal.org/project/ai_search) which is a drop-in replacement and target of all new development. It also had the same vulnerability.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This vulnerability is mitigated by the fact that:&lt;/p&gt;
&lt;p&gt;* The AI Search submodule must be enabled and used with a Search API view.
* The view must use Search API result caching (&amp;#34;Search API (time-based)&amp;#34;, &amp;#34;Search API (tag-based)&amp;#34; or &amp;#34;Search API (time and tag-based)&amp;#34;). The default, &amp;#34;Search API (none)&amp;#34;, is not affected.
* A user with access to the restricted content must have run the same search within the cache lifetime.&lt;/p&gt;
&lt;p&gt;Retrieval-augmented generation (RAG) tools, AI Assistant RAG actions and custom code running Search API queries are not affected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/drupal-contrib-2026-270</guid>
    </item>
    <item>
      <title>fkie_cve-2026-118550</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-118550</link>
      <description>&lt;p&gt;Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal AI (Artificial Intelligence) allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects AI (Artificial Intelligence) versions: from 0.0.0 to 1.4.11, from 1.5.0 to 1.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal AI (Artificial Intelligence) allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects AI (Artificial Intelligence) versions: from 0.0.0 to 1.4.11, from 1.5.0 to 1.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-118550</guid>
    </item>
    <item>
      <title>GHSA-jqpj-2gpx-ffr5</title>
      <link>https://db.gcve.eu/vuln/ghsa-jqpj-2gpx-ffr5</link>
      <description>&lt;p&gt;Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal AI (Artificial Intelligence) allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects AI (Artificial Intelligence) versions: from 0.0.0 to 1.4.11, from 1.5.0 to 1.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal AI (Artificial Intelligence) allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects AI (Artificial Intelligence) versions: from 0.0.0 to 1.4.11, from 1.5.0 to 1.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-jqpj-2gpx-ffr5</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4230 — Drupal Erweiterungen: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4230</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Drupal ausnutzen, um erweiterte Berechtigungen zu erlangen und Benutzerkonten zu übernehmen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen und nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Drupal ausnutzen, um erweiterte Berechtigungen zu erlangen und Benutzerkonten zu übernehmen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen und nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4230</guid>
    </item>
  </channel>
</rss>
