<?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>Sun, 04 Oct 2026 06:15:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-01735</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-01735</link>
      <description>bdu:2023-01735</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-01735</guid>
    </item>
    <item>
      <title>BIT-mlflow-2023-1177 — Path Traversal: '\..\filename' in mlflow/mlflow</title>
      <link>https://cve.radiocsirt.org/vuln/bit-mlflow-2023-1177</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: mlflow&lt;/p&gt;
&lt;p&gt;Path Traversal: &amp;#39;\..\filename&amp;#39; in GitHub repository mlflow/mlflow prior to 2.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: mlflow&lt;/p&gt;
&lt;p&gt;Path Traversal: &amp;#39;\..\filename&amp;#39; in GitHub repository mlflow/mlflow prior to 2.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-mlflow-2023-1177</guid>
    </item>
    <item>
      <title>EUVD-2026-218418</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-218418</link>
      <description>EUVD-2026-218418</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-218418</guid>
    </item>
    <item>
      <title>fkie_cve-2023-1177</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-1177</link>
      <description>&lt;p&gt;Path Traversal: &amp;#39;\..\filename&amp;#39; in GitHub repository mlflow/mlflow prior to 2.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Path Traversal: &amp;#39;\..\filename&amp;#39; in GitHub repository mlflow/mlflow prior to 2.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-1177</guid>
    </item>
    <item>
      <title>GHSA-xg73-94fp-g449 — mlflow is vulnerable to remote file access in `mlflow server` and `mlflow ui` CLIs</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xg73-94fp-g449</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mlflow&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Users of the MLflow Open Source Project who are hosting the MLflow Model Registry using the `mlflow server` or `mlflow ui` commands using an MLflow version older than MLflow 2.2.1 may be vulnerable to a remote file access exploit if they are not limiting who can query their server (for example, by using a cloud VPC, an IP allowlist for inbound requests, or authentication / authorization middleware).&lt;/p&gt;
&lt;p&gt;This issue only affects users and integrations that run the `mlflow server` and `mlflow ui` commands. Integrations that do not make use of `mlflow server` or `mlflow ui` are unaffected; for example, the Databricks Managed MLflow product and MLflow on Azure Machine Learning do not make use of these commands and are not impacted by these vulnerabilities in any way.&lt;/p&gt;
&lt;p&gt;The vulnerability detailed in https://nvd.nist.gov/vuln/detail/CVE-2023-1177 enables an actor to download arbitrary files unrelated to MLflow from the host server, including any files stored in remote locations to which the host server has access.&lt;/p&gt;
&lt;p&gt;### Patches
This vulnerability has been patched in MLflow 2.2.1, which was released to PyPI on March 2nd, 2023. If you are using `mlflow server` or `mlflow ui` with the MLflow Model Registry, we recommend upgrading to MLflow 2.2.1 as soon as possible.&lt;/p&gt;
&lt;p&gt;### Workarounds
If you are using the MLflow open source `mlflow server` or `mlflow ui` commands, we strongly recommend limiting who can access your MLflow Model Registry and MLflow Tracking servers using a cloud VP…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mlflow&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Users of the MLflow Open Source Project who are hosting the MLflow Model Registry using the `mlflow server` or `mlflow ui` commands using an MLflow version older than MLflow 2.2.1 may be vulnerable to a remote file access exploit if they are not limiting who can query their server (for example, by using a cloud VPC, an IP allowlist for inbound requests, or authentication / authorization middleware).&lt;/p&gt;
&lt;p&gt;This issue only affects users and integrations that run the `mlflow server` and `mlflow ui` commands. Integrations that do not make use of `mlflow server` or `mlflow ui` are unaffected; for example, the Databricks Managed MLflow product and MLflow on Azure Machine Learning do not make use of these commands and are not impacted by these vulnerabilities in any way.&lt;/p&gt;
&lt;p&gt;The vulnerability detailed in https://nvd.nist.gov/vuln/detail/CVE-2023-1177 enables an actor to download arbitrary files unrelated to MLflow from the host server, including any files stored in remote locations to which the host server has access.&lt;/p&gt;
&lt;p&gt;### Patches
This vulnerability has been patched in MLflow 2.2.1, which was released to PyPI on March 2nd, 2023. If you are using `mlflow server` or `mlflow ui` with the MLflow Model Registry, we recommend upgrading to MLflow 2.2.1 as soon as possible.&lt;/p&gt;
&lt;p&gt;### Workarounds
If you are using the MLflow open source `mlflow server` or `mlflow ui` commands, we strongly recommend limiting who can access your MLflow Model Registry and MLflow Tracking servers using a cloud VP…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xg73-94fp-g449</guid>
    </item>
    <item>
      <title>gsd-2023-1177</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-1177</link>
      <description>gsd-2023-1177</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-1177</guid>
    </item>
    <item>
      <title>PYSEC-2023-29</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-29</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mlflow&lt;/p&gt;
&lt;p&gt;Path Traversal: &amp;#39;\..\filename&amp;#39; in GitHub repository mlflow/mlflow prior to 2.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mlflow&lt;/p&gt;
&lt;p&gt;Path Traversal: &amp;#39;\..\filename&amp;#39; in GitHub repository mlflow/mlflow prior to 2.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-29</guid>
    </item>
  </channel>
</rss>
