<?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 23:55:29 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-07995</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-07995</link>
      <description>bdu:2026-07995</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-07995</guid>
    </item>
    <item>
      <title>EUVD-2026-272074</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-272074</link>
      <description>EUVD-2026-272074</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-272074</guid>
    </item>
    <item>
      <title>fkie_cve-2025-9905</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-9905</link>
      <description>&lt;p&gt;The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True.&lt;/p&gt;
&lt;p&gt;One can create a specially crafted .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed.&lt;/p&gt;
&lt;p&gt;This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives.&lt;/p&gt;
&lt;p&gt;Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True.&lt;/p&gt;
&lt;p&gt;One can create a specially crafted .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed.&lt;/p&gt;
&lt;p&gt;This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives.&lt;/p&gt;
&lt;p&gt;Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-9905</guid>
    </item>
    <item>
      <title>GHSA-36rr-ww3j-vrjv — The Keras `Model.load_model` method **silently** ignores `safe_mode=True` and allows arbitrary code execution when a `.…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-36rr-ww3j-vrjv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keras&lt;/p&gt;
&lt;p&gt;**Note:** This report has already been discussed with the Google OSS VRP team, who recommended that I reach out directly to the Keras team. I’ve chosen to do so privately rather than opening a public issue, due to the potential security implications. I also attempted to use the email address listed in your `SECURITY.md`, but received no response.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a model in the `.h5` (or `.hdf5`) format is loaded using the Keras `Model.load_model` method, the `safe_mode=True` setting is **silently** ignored without any warning or error. This allows an attacker to execute arbitrary code on the victim’s machine with the same privileges as the Keras application. This report is specific to the `.h5`/`.hdf5` file format. The attack works regardless of the other parameters passed to `load_model` and does not require any sophisticated technique—`.h5` and `.hdf5` files are simply not checked for unsafe code execution.&lt;/p&gt;
&lt;p&gt;From this point on, I will refer only to the `.h5` file format, though everything equally applies to `.hdf5`.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Intended behaviour 
According to the official Keras documentation, `safe_mode` is defined as:&lt;/p&gt;
&lt;p&gt;```
safe_mode: Boolean, whether to disallow unsafe lambda deserialization. When safe_mode=False, loading an object has the potential to trigger arbitrary code execution. This argument is only applicable to the Keras v3 model format. Defaults to True.
```
I understand that the behavior described in this report is somehow **intentional**, as `saf…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keras&lt;/p&gt;
&lt;p&gt;**Note:** This report has already been discussed with the Google OSS VRP team, who recommended that I reach out directly to the Keras team. I’ve chosen to do so privately rather than opening a public issue, due to the potential security implications. I also attempted to use the email address listed in your `SECURITY.md`, but received no response.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a model in the `.h5` (or `.hdf5`) format is loaded using the Keras `Model.load_model` method, the `safe_mode=True` setting is **silently** ignored without any warning or error. This allows an attacker to execute arbitrary code on the victim’s machine with the same privileges as the Keras application. This report is specific to the `.h5`/`.hdf5` file format. The attack works regardless of the other parameters passed to `load_model` and does not require any sophisticated technique—`.h5` and `.hdf5` files are simply not checked for unsafe code execution.&lt;/p&gt;
&lt;p&gt;From this point on, I will refer only to the `.h5` file format, though everything equally applies to `.hdf5`.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Intended behaviour 
According to the official Keras documentation, `safe_mode` is defined as:&lt;/p&gt;
&lt;p&gt;```
safe_mode: Boolean, whether to disallow unsafe lambda deserialization. When safe_mode=False, loading an object has the potential to trigger arbitrary code execution. This argument is only applicable to the Keras v3 model format. Defaults to True.
```
I understand that the behavior described in this report is somehow **intentional**, as `saf…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-36rr-ww3j-vrjv</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-9905 — Arbitary Code execution in Keras load_model()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-9905</link>
      <description>msrc_CVE-2025-9905</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-9905</guid>
    </item>
    <item>
      <title>PYSEC-2025-123</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2025-123</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keras&lt;/p&gt;
&lt;p&gt;The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True.&lt;/p&gt;
&lt;p&gt;One can create a specially crafted .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed.&lt;/p&gt;
&lt;p&gt;This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives.&lt;/p&gt;
&lt;p&gt;Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: keras&lt;/p&gt;
&lt;p&gt;The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True.&lt;/p&gt;
&lt;p&gt;One can create a specially crafted .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed.&lt;/p&gt;
&lt;p&gt;This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives.&lt;/p&gt;
&lt;p&gt;Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2025-123</guid>
    </item>
    <item>
      <title>RHSA-2025:22759 — Red Hat Security Advisory: RHOAI 2.22.3 - Red Hat OpenShift AI</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:22759</link>
      <description>&lt;p&gt;keras: Arbitary Code execution in Keras load_model() keras: Keras Path Traversal Vulnerability database/sql: Postgres Scan Race Condition aiohttp: AIOHTTP HTTP Request/Response Smuggling golang: archive/tar: Unbounded allocation when parsing GNU sparse map axios: Axios DoS via lack of data size check github.com/argoproj/argo-workflows: Argo Workflows Zip Slip starlette: Starlette DoS via Range header merging&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;keras: Arbitary Code execution in Keras load_model() keras: Keras Path Traversal Vulnerability database/sql: Postgres Scan Race Condition aiohttp: AIOHTTP HTTP Request/Response Smuggling golang: archive/tar: Unbounded allocation when parsing GNU sparse map axios: Axios DoS via lack of data size check github.com/argoproj/argo-workflows: Argo Workflows Zip Slip starlette: Starlette DoS via Range header merging&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:22759</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-9905</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-9905</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: keras, Ubuntu:20.04:LTS: keras&lt;/p&gt;
&lt;p&gt;The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True. One can create a specially crafted .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed. This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives. Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: keras, Ubuntu:20.04:LTS: keras&lt;/p&gt;
&lt;p&gt;The Keras Model.load_model method can be exploited to achieve arbitrary code execution, even with safe_mode=True. One can create a specially crafted .h5/.hdf5 model archive that, when loaded via Model.load_model, will trigger arbitrary code to be executed. This is achieved by crafting a special .h5 archive file that uses the Lambda layer feature of keras which allows arbitrary Python code in the form of pickled code. The vulnerability comes from the fact that the safe_mode=True option is not honored when reading .h5 archives. Note that the .h5/.hdf5 format is a legacy format supported by Keras 3 for backwards compatibility.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-9905</guid>
    </item>
  </channel>
</rss>
