<?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>Sun, 04 Oct 2026 22:03:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-81817 — Flowintel Missing Task-to-Case Authorization Allows Cross-Case Task Modification</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-81817</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; flowintel&lt;/p&gt;
&lt;p&gt;Affected versions of Flowintel contain an insecure direct object reference / broken object-level authorization issue across numerous task endpoints.&lt;/p&gt;
&lt;p&gt;The routes generally received both a case identifier and a task identifier, but previously they did not enforce that the task actually belonged to the supplied case. As a result, an authenticated user with editor-level access to one case could potentially substitute the ID of a task from another case and invoke operations against that foreign task.&lt;/p&gt;
&lt;p&gt;The patch introduces task_case_bound_required, which loads both objects and returns 404 unless the task belongs to the requested case. This protection is applied to edit, delete, note, assignment, status, file, export, MISP-linking, subtask, external-reference, and other task-related endpoints.&lt;/p&gt;
&lt;p&gt;The fix also adds explicit checks that a requested note_id belongs to the current task before returning or exporting it, closing related cross-object access paths.&lt;/p&gt;
&lt;p&gt;Version impacted =&amp;gt;3.3.0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; flowintel&lt;/p&gt;
&lt;p&gt;Affected versions of Flowintel contain an insecure direct object reference / broken object-level authorization issue across numerous task endpoints.&lt;/p&gt;
&lt;p&gt;The routes generally received both a case identifier and a task identifier, but previously they did not enforce that the task actually belonged to the supplied case. As a result, an authenticated user with editor-level access to one case could potentially substitute the ID of a task from another case and invoke operations against that foreign task.&lt;/p&gt;
&lt;p&gt;The patch introduces task_case_bound_required, which loads both objects and returns 404 unless the task belongs to the requested case. This protection is applied to edit, delete, note, assignment, status, file, export, MISP-linking, subtask, external-reference, and other task-related endpoints.&lt;/p&gt;
&lt;p&gt;The fix also adds explicit checks that a requested note_id belongs to the current task before returning or exporting it, closing related cross-object access paths.&lt;/p&gt;
&lt;p&gt;Version impacted =&amp;gt;3.3.0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-81817</guid>
    </item>
  </channel>
</rss>
