<?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, 14 Oct 2026 20:33:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48593 — Unbounded range expansion in cron describe causes memory exhaustion in oban_web</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-48593</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; oban-bg oban_web&lt;/p&gt;
&lt;p&gt;Uncontrolled Resource Consumption vulnerability in oban-bg oban_web (&amp;#39;Elixir.Oban.Web.CronExpr&amp;#39; modules) allows memory exhaustion via unbounded cron range expansion.&lt;/p&gt;
&lt;p&gt;An attacker with access to schedule cron jobs can submit a malicious cron expression such as &amp;#34;0 0 1-100000000 * *&amp;#34;. When a user with dashboard access views the cron job list, &amp;#39;Elixir.Oban.Web.CronExpr&amp;#39;:describe/1 is called to render the expression. parse_range/1 parses both range endpoints via Integer.parse/1 with no bounds check, and the downstream helpers expand_dom_parts/1 and expand_dow_parts/1 materialise the range eagerly via Enum.to_list/1, causing allocation of ~2.4 GB and stalling or crashing the BEAM node. A sibling helper extract_dom_values already validates range bounds, but the expansion helpers do not.&lt;/p&gt;
&lt;p&gt;This issue affects oban_web: from 2.12.0 before 2.12.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; oban-bg oban_web&lt;/p&gt;
&lt;p&gt;Uncontrolled Resource Consumption vulnerability in oban-bg oban_web (&amp;#39;Elixir.Oban.Web.CronExpr&amp;#39; modules) allows memory exhaustion via unbounded cron range expansion.&lt;/p&gt;
&lt;p&gt;An attacker with access to schedule cron jobs can submit a malicious cron expression such as &amp;#34;0 0 1-100000000 * *&amp;#34;. When a user with dashboard access views the cron job list, &amp;#39;Elixir.Oban.Web.CronExpr&amp;#39;:describe/1 is called to render the expression. parse_range/1 parses both range endpoints via Integer.parse/1 with no bounds check, and the downstream helpers expand_dom_parts/1 and expand_dow_parts/1 materialise the range eagerly via Enum.to_list/1, causing allocation of ~2.4 GB and stalling or crashing the BEAM node. A sibling helper extract_dom_values already validates range bounds, but the expansion helpers do not.&lt;/p&gt;
&lt;p&gt;This issue affects oban_web: from 2.12.0 before 2.12.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-48593</guid>
    </item>
  </channel>
</rss>
