<?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 10:04:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-78228 — Unbounded handle_error recursion enables denial of service in AshOban triggers</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-78228</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_oban&lt;/p&gt;
&lt;p&gt;Uncontrolled Recursion vulnerability in ash-project ash_oban allows a user who can drive a trigger&amp;#39;s on_error action to fail on the final attempt to exhaust worker CPU and memory, denying service.&lt;/p&gt;
&lt;p&gt;The generated worker&amp;#39;s atomic handle_error/4 runs the trigger&amp;#39;s on_error action on a job&amp;#39;s final attempt inside a rescue that, when the action itself raises, calls handle_error/4 again with the same job. The job&amp;#39;s attempt still equals max_attempts, so it re-enters the same clause and re-runs the failing action, with no exit. Any deterministic on_error failure (a data-layer outage, a misconfigured action, or a record the action rejects) loops forever; because the recursive call is not in tail position, each iteration retains a formatted stacktrace and the process heap grows without bound while the failing statement is re-issued against the data layer until the runtime kills the worker.&lt;/p&gt;
&lt;p&gt;This issue affects ash_oban: from 0.8.0-rc.1 before 0.8.14.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_oban&lt;/p&gt;
&lt;p&gt;Uncontrolled Recursion vulnerability in ash-project ash_oban allows a user who can drive a trigger&amp;#39;s on_error action to fail on the final attempt to exhaust worker CPU and memory, denying service.&lt;/p&gt;
&lt;p&gt;The generated worker&amp;#39;s atomic handle_error/4 runs the trigger&amp;#39;s on_error action on a job&amp;#39;s final attempt inside a rescue that, when the action itself raises, calls handle_error/4 again with the same job. The job&amp;#39;s attempt still equals max_attempts, so it re-enters the same clause and re-runs the failing action, with no exit. Any deterministic on_error failure (a data-layer outage, a misconfigured action, or a record the action rejects) loops forever; because the recursive call is not in tail position, each iteration retains a formatted stacktrace and the process heap grows without bound while the failing statement is re-issued against the data layer until the runtime kills the worker.&lt;/p&gt;
&lt;p&gt;This issue affects ash_oban: from 0.8.0-rc.1 before 0.8.14.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-78228</guid>
    </item>
  </channel>
</rss>
