<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 12:00:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-55611 — AnythingLLM: embed-parsed-file cleanup deletes any parsed file by ID without ownership scoping (cross-tenant IDOR delet…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-55611</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Mintplex-Labs anything-llm&lt;/p&gt;
&lt;p&gt;AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. From 1.11.1 until 1.14.1, userId/workspaceId scoping to the parsed-files read/delete paths was added. However, the POST /api/workspace/:slug/embed-parsed-file/:fileId flow still deletes the target file by primary key only, with no ownership check, inside two finally{} blocks that run even when the ownership-checked read fails. As a result a manager or admin (multi-user mode) can delete any other user&amp;#39;s parsed file in any workspace — including workspaces they are not a member of — by enumerating integer fileIds. The server even returns &amp;#34;File not found&amp;#34; while still deleting the file. This vulnerability is fixed in 1.14.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Mintplex-Labs anything-llm&lt;/p&gt;
&lt;p&gt;AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. From 1.11.1 until 1.14.1, userId/workspaceId scoping to the parsed-files read/delete paths was added. However, the POST /api/workspace/:slug/embed-parsed-file/:fileId flow still deletes the target file by primary key only, with no ownership check, inside two finally{} blocks that run even when the ownership-checked read fails. As a result a manager or admin (multi-user mode) can delete any other user&amp;#39;s parsed file in any workspace — including workspaces they are not a member of — by enumerating integer fileIds. The server even returns &amp;#34;File not found&amp;#34; while still deleting the file. This vulnerability is fixed in 1.14.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-55611</guid>
    </item>
  </channel>
</rss>
