<?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>Fri, 02 Oct 2026 12:27:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-361088</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361088</link>
      <description>EUVD-2026-361088</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361088</guid>
    </item>
    <item>
      <title>fkie_cve-2026-44513</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-44513</link>
      <description>&lt;p&gt;Diffusers is the a library for  pretrained diffusion models. Prior to 0.38.0, a trust_remote_code bypass in DiffusionPipeline.from_pretrained allows arbitrary remote code execution despite the user passing trust_remote_code=False (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the trust_remote_code gate was implemented inside DiffusionPipeline.download() rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited download() also bypassed the security check. DiffusionPipeline.from_pretrained(&amp;#39;repoA&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the gate evaluated against repoA&amp;#39;s file list rather than repoB&amp;#39;s, so repoB&amp;#39;s pipeline.py was loaded and executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the local-path branch never invoked download(), so the gate was never reached and remote code from repoB executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, trust_remote_code=False) where the snapshot contains custom component files (e.g. unet/my_unet_model.py) referenced from model_index.json — same root cause; the local path skipped download() and custom component code executed. This vulnerability is fixed in 0.38.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Diffusers is the a library for  pretrained diffusion models. Prior to 0.38.0, a trust_remote_code bypass in DiffusionPipeline.from_pretrained allows arbitrary remote code execution despite the user passing trust_remote_code=False (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the trust_remote_code gate was implemented inside DiffusionPipeline.download() rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited download() also bypassed the security check. DiffusionPipeline.from_pretrained(&amp;#39;repoA&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the gate evaluated against repoA&amp;#39;s file list rather than repoB&amp;#39;s, so repoB&amp;#39;s pipeline.py was loaded and executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the local-path branch never invoked download(), so the gate was never reached and remote code from repoB executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, trust_remote_code=False) where the snapshot contains custom component files (e.g. unet/my_unet_model.py) referenced from model_index.json — same root cause; the local path skipped download() and custom component code executed. This vulnerability is fixed in 0.38.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-44513</guid>
    </item>
    <item>
      <title>GHSA-98h9-4798-4q5v — Diffusers has a `trust_remote_code` bypass via `custom_pipeline` and local custom components</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-98h9-4798-4q5v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: diffusers&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A `trust_remote_code` bypass in `DiffusionPipeline.from_pretrained` allows arbitrary remote code execution despite the user passing `trust_remote_code=False` (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the `trust_remote_code` gate was implemented inside `DiffusionPipeline.download()` rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited `download()` also bypassed the security check:&lt;/p&gt;
&lt;p&gt;1. **Cross-repo `custom_pipeline`.** `DiffusionPipeline.from_pretrained(&amp;#39;repoA&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False)` — the gate evaluated against `repoA`&amp;#39;s file list rather than `repoB`&amp;#39;s, so `repoB`&amp;#39;s `pipeline.py` was loaded and executed.
2. **Local snapshot + Hub `custom_pipeline`.** `DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False)` — the local-path branch never invoked `download()`, so the gate was never reached and remote code from `repoB` executed.
3. **Local snapshot with custom components.** `DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, trust_remote_code=False)` where the snapshot contains custom component files (e.g. `unet/my_unet_model.py`) referenced from `model_index.json` — same root cause; the local path skipped `download()` and custom component code executed.&lt;/p&gt;
&lt;p&gt;Silent remote code execution on the victim&amp;#39;s machine. Anyone calling `DiffusionPipeline.from_pretraine…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: diffusers&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A `trust_remote_code` bypass in `DiffusionPipeline.from_pretrained` allows arbitrary remote code execution despite the user passing `trust_remote_code=False` (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the `trust_remote_code` gate was implemented inside `DiffusionPipeline.download()` rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited `download()` also bypassed the security check:&lt;/p&gt;
&lt;p&gt;1. **Cross-repo `custom_pipeline`.** `DiffusionPipeline.from_pretrained(&amp;#39;repoA&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False)` — the gate evaluated against `repoA`&amp;#39;s file list rather than `repoB`&amp;#39;s, so `repoB`&amp;#39;s `pipeline.py` was loaded and executed.
2. **Local snapshot + Hub `custom_pipeline`.** `DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False)` — the local-path branch never invoked `download()`, so the gate was never reached and remote code from `repoB` executed.
3. **Local snapshot with custom components.** `DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, trust_remote_code=False)` where the snapshot contains custom component files (e.g. `unet/my_unet_model.py`) referenced from `model_index.json` — same root cause; the local path skipped `download()` and custom component code executed.&lt;/p&gt;
&lt;p&gt;Silent remote code execution on the victim&amp;#39;s machine. Anyone calling `DiffusionPipeline.from_pretraine…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-98h9-4798-4q5v</guid>
    </item>
    <item>
      <title>PYSEC-2026-40</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-40</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: diffusers&lt;/p&gt;
&lt;p&gt;Diffusers is the a library for  pretrained diffusion models. Prior to 0.38.0, a trust_remote_code bypass in DiffusionPipeline.from_pretrained allows arbitrary remote code execution despite the user passing trust_remote_code=False (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the trust_remote_code gate was implemented inside DiffusionPipeline.download() rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited download() also bypassed the security check. DiffusionPipeline.from_pretrained(&amp;#39;repoA&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the gate evaluated against repoA&amp;#39;s file list rather than repoB&amp;#39;s, so repoB&amp;#39;s pipeline.py was loaded and executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the local-path branch never invoked download(), so the gate was never reached and remote code from repoB executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, trust_remote_code=False) where the snapshot contains custom component files (e.g. unet/my_unet_model.py) referenced from model_index.json — same root cause; the local path skipped download() and custom component code executed. This vulnerability is fixed in 0.38.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: diffusers&lt;/p&gt;
&lt;p&gt;Diffusers is the a library for  pretrained diffusion models. Prior to 0.38.0, a trust_remote_code bypass in DiffusionPipeline.from_pretrained allows arbitrary remote code execution despite the user passing trust_remote_code=False (or omitting it, which is the default). The vulnerability has three variants, all sharing the same root cause — the trust_remote_code gate was implemented inside DiffusionPipeline.download() rather than at the actual dynamic-module load site, so any code path that bypassed or short-circuited download() also bypassed the security check. DiffusionPipeline.from_pretrained(&amp;#39;repoA&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the gate evaluated against repoA&amp;#39;s file list rather than repoB&amp;#39;s, so repoB&amp;#39;s pipeline.py was loaded and executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, custom_pipeline=&amp;#39;attacker/repoB&amp;#39;, trust_remote_code=False) — the local-path branch never invoked download(), so the gate was never reached and remote code from repoB executed. DiffusionPipeline.from_pretrained(&amp;#39;/local/snapshot&amp;#39;, trust_remote_code=False) where the snapshot contains custom component files (e.g. unet/my_unet_model.py) referenced from model_index.json — same root cause; the local path skipped download() and custom component code executed. This vulnerability is fixed in 0.38.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-40</guid>
    </item>
    <item>
      <title>RHSA-2026:60520 — Red Hat Security Advisory: RHOAI 3.4.4 - Red Hat OpenShift AI</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:60520</link>
      <description>&lt;p&gt;urllib3: urllib3 Streaming API improperly handles highly compressed data github.com/argoproj/argo-workflows: argoproj/argo-workflows is vulnerable to RCE via ZipSlip and symbolic links image-size: image-size: Denial of Service via crafted image buffer with zero-valued size field image-size: image-size: Denial of Service via crafted ICNS image buffer mlflow/mlflow: mlflow/mlflow: Unauthenticated remote code execution via unprotected job endpoints mlflow: mlflow: Arbitrary file read via bypassed source path validation python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting jupyter-server: jupyter-server: Sensitive data exposure via path traversal vulnerability fast-uri: fast-uri: URI authority bypass due to improper delimiter handling undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy form-data: form-data: Form field override via CRLF injection undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames nltk: NLTK: Information disclosure via path traversal vulnerability keras: Keras: Arbitrary code execution via deserialization vulnerability brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity shell-quo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;urllib3: urllib3 Streaming API improperly handles highly compressed data github.com/argoproj/argo-workflows: argoproj/argo-workflows is vulnerable to RCE via ZipSlip and symbolic links image-size: image-size: Denial of Service via crafted image buffer with zero-valued size field image-size: image-size: Denial of Service via crafted ICNS image buffer mlflow/mlflow: mlflow/mlflow: Unauthenticated remote code execution via unprotected job endpoints mlflow: mlflow: Arbitrary file read via bypassed source path validation python-transformers: python-transformers: Arbitrary code execution due to overridden trust_remote_code setting jupyter-server: jupyter-server: Sensitive data exposure via path traversal vulnerability fast-uri: fast-uri: URI authority bypass due to improper delimiter handling undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy form-data: form-data: Form field override via CRLF injection undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames nltk: NLTK: Information disclosure via path traversal vulnerability keras: Keras: Arbitrary code execution via deserialization vulnerability brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity shell-quo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:60520</guid>
    </item>
  </channel>
</rss>
