<?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>Thu, 15 Oct 2026 05:32:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-322102</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-322102</link>
      <description>EUVD-2026-322102</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-322102</guid>
    </item>
    <item>
      <title>fkie_cve-2026-48592</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48592</link>
      <description>&lt;p&gt;Missing Authorization vulnerability in oban-bg oban_web (&amp;#39;Elixir.Oban.Web.Jobs.DetailComponent&amp;#39; modules) allows unauthorized job worker substitution.&lt;/p&gt;
&lt;p&gt;The handle_event(&amp;#34;save-job&amp;#34;, ...) handler in &amp;#39;Elixir.Oban.Web.Jobs.DetailComponent&amp;#39; does not perform an authorization check, unlike the sibling cancel, delete, and retry handlers which all verify the caller&amp;#39;s privileges via can?/2. An authenticated user with :read_only access can push a forged save-job LiveView WebSocket event to overwrite a job&amp;#39;s worker field with any other existing Oban.Worker module in the application. On the job&amp;#39;s next execution attempt, Oban will invoke perform/1 on the attacker-chosen module instead of the intended one.&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;Missing Authorization vulnerability in oban-bg oban_web (&amp;#39;Elixir.Oban.Web.Jobs.DetailComponent&amp;#39; modules) allows unauthorized job worker substitution.&lt;/p&gt;
&lt;p&gt;The handle_event(&amp;#34;save-job&amp;#34;, ...) handler in &amp;#39;Elixir.Oban.Web.Jobs.DetailComponent&amp;#39; does not perform an authorization check, unlike the sibling cancel, delete, and retry handlers which all verify the caller&amp;#39;s privileges via can?/2. An authenticated user with :read_only access can push a forged save-job LiveView WebSocket event to overwrite a job&amp;#39;s worker field with any other existing Oban.Worker module in the application. On the job&amp;#39;s next execution attempt, Oban will invoke perform/1 on the attacker-chosen module instead of the intended one.&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/fkie_cve-2026-48592</guid>
    </item>
    <item>
      <title>GHSA-389x-rgxr-8m33 — oban_web missing authorization check on `save-job` event handler</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-389x-rgxr-8m33</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hex: oban_web&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`oban_web` 2.12.0 through the current unpatched release exposes a `save-job` LiveView event handler that performs no authorization check, allowing any authenticated user (including those with `:read_only` access) to overwrite a queued job&amp;#39;s `worker` field with any other `Oban.Worker` module present in the application. On the job&amp;#39;s next execution attempt, Oban dispatches `perform/1` on the attacker-chosen module instead of the intended one.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `lib/oban/web/live/jobs/detail_component.ex`, the sibling event handlers for destructive actions all gate their side effects via `can?/2` (cancel, delete, retry). The `handle_event(&amp;#34;save-job&amp;#34;, params, socket)` clause added in 2.12.0 has no equivalent guard. It builds a `changes` map from the client-supplied params (including `worker`, `queue`, `priority`, `max_attempts`, `scheduled_at`, `tags`, `args`) and unconditionally dispatches `{:update_job, job, changes}` to the parent LiveView, which writes the changes to the database.&lt;/p&gt;
&lt;p&gt;The `disabled` attribute on the edit fieldset and button in the rendered HTML is advisory only. The Phoenix LiveView channel dispatches any `phx-event` pushed over the authenticated WebSocket regardless of what the DOM looks like, so the attacker pushes the event directly over the WebSocket without touching the UI.&lt;/p&gt;
&lt;p&gt;The attacker is constrained to substituting an existing `Oban.Worker` module already loaded in the application (no code injection). The impact depends on what workers are av…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hex: oban_web&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`oban_web` 2.12.0 through the current unpatched release exposes a `save-job` LiveView event handler that performs no authorization check, allowing any authenticated user (including those with `:read_only` access) to overwrite a queued job&amp;#39;s `worker` field with any other `Oban.Worker` module present in the application. On the job&amp;#39;s next execution attempt, Oban dispatches `perform/1` on the attacker-chosen module instead of the intended one.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In `lib/oban/web/live/jobs/detail_component.ex`, the sibling event handlers for destructive actions all gate their side effects via `can?/2` (cancel, delete, retry). The `handle_event(&amp;#34;save-job&amp;#34;, params, socket)` clause added in 2.12.0 has no equivalent guard. It builds a `changes` map from the client-supplied params (including `worker`, `queue`, `priority`, `max_attempts`, `scheduled_at`, `tags`, `args`) and unconditionally dispatches `{:update_job, job, changes}` to the parent LiveView, which writes the changes to the database.&lt;/p&gt;
&lt;p&gt;The `disabled` attribute on the edit fieldset and button in the rendered HTML is advisory only. The Phoenix LiveView channel dispatches any `phx-event` pushed over the authenticated WebSocket regardless of what the DOM looks like, so the attacker pushes the event directly over the WebSocket without touching the UI.&lt;/p&gt;
&lt;p&gt;The attacker is constrained to substituting an existing `Oban.Worker` module already loaded in the application (no code injection). The impact depends on what workers are av…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-389x-rgxr-8m33</guid>
    </item>
  </channel>
</rss>
