<?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>Mon, 28 Sep 2026 20:55:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-100177 — Ail Framework Crawler: Missing Cookiejar Authorization Check Allows Cross-Organization Cookiejar Attachment</title>
      <link>https://db.gcve.eu/vuln/cve-2026-100177</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ail project ail framework&lt;/p&gt;
&lt;p&gt;The AIL Framework crawler task creation API (api_add_crawler_task) contained an insufficient authorization check when a user supplied a cookiejar UUID to attach to a one-shot or scheduled crawler task. The original code only verified that the cookiejar existed and, if its access level was 0, compared the cookiejar&amp;#39;s owning user ID to the requesting user ID. It did not validate organizational boundaries, did not account for the requesting user&amp;#39;s role. When the cookiejar level was not 0, no access check was performed at all. An authenticated user could therefore reference another organization&amp;#39;s cookiejar by UUID and have the crawler use that organization&amp;#39;s stored cookies (session tokens, authentication credentials) when performing web crawls, effectively leaking or exfiltrating the victim organization&amp;#39;s session data.&lt;/p&gt;
&lt;p&gt;The vulnerability requires an authenticated user with the ability to create crawler tasks. The attacker must know or guess a valid cookiejar UUID belonging to another organization. The impact is unauthorized access to another organization&amp;#39;s stored cookies and session data through the crawler infrastructure.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ail project ail framework&lt;/p&gt;
&lt;p&gt;The AIL Framework crawler task creation API (api_add_crawler_task) contained an insufficient authorization check when a user supplied a cookiejar UUID to attach to a one-shot or scheduled crawler task. The original code only verified that the cookiejar existed and, if its access level was 0, compared the cookiejar&amp;#39;s owning user ID to the requesting user ID. It did not validate organizational boundaries, did not account for the requesting user&amp;#39;s role. When the cookiejar level was not 0, no access check was performed at all. An authenticated user could therefore reference another organization&amp;#39;s cookiejar by UUID and have the crawler use that organization&amp;#39;s stored cookies (session tokens, authentication credentials) when performing web crawls, effectively leaking or exfiltrating the victim organization&amp;#39;s session data.&lt;/p&gt;
&lt;p&gt;The vulnerability requires an authenticated user with the ability to create crawler tasks. The attacker must know or guess a valid cookiejar UUID belonging to another organization. The impact is unauthorized access to another organization&amp;#39;s stored cookies and session data through the crawler infrastructure.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-100177</guid>
    </item>
  </channel>
</rss>
