<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T00:01:40.731333+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2023-43654</id>
    <title>CVE-2023-43654 — TorchServe Server-Side Request Forgery</title>
    <updated>2026-10-04T00:01:40.733012+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> pytorch serve, pytorch torchserve</p>
<p>TorchServe is a tool for serving and scaling PyTorch models in production. TorchServe default configuration lacks proper input validation, enabling third parties to invoke remote HTTP download requests and write files to the disk. This issue could be taken advantage of to compromise the integrity of the system and sensitive data. This issue is present in versions 0.1.0 to 0.8.1. A user is able to load the model of their choice from any URL that they would like to use. The user of TorchServe is responsible for configuring both the allowed_urls and specifying the model URL to be used. A pull request to warn the user when the default value for allowed_urls is used has been merged in PR #2534. TorchServe release 0.8.2 includes this change. Users are advised to upgrade. There are no known workarounds for this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2023-43654"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-8fxr-qfr9-p34w</id>
    <title>GHSA-8fxr-qfr9-p34w — TorchServe Server-Side Request Forgery vulnerability</title>
    <updated>2026-10-04T00:01:40.733070+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: torchserve</p>
<p>## Impact
**Remote Server-Side Request Forgery (SSRF)**
    **Issue**: TorchServe default configuration lacks proper input validation, enabling third parties to invoke remote HTTP download requests and write files to the disk. This issue could be taken advantage of to compromise the integrity of the system and sensitive data. This issue is present in versions `0.1.0` to `0.8.1`.
    **Mitigation**: The user is able to load the model of their choice from any URL that they would like to use. The user of TorchServe is responsible for configuring both the [allowed_urls](https://github.com/pytorch/serve/blob/b3eced56b4d9d5d3b8597aa506a0bcf954d291bc/docs/configuration.md?plain=1#L296) and specifying the model URL to be used. A pull request to warn the user when the default value for `allowed_urls` is used has been merged - https://github.com/pytorch/serve/pull/2534. TorchServe release `0.8.2` includes this change.</p>
<p>## Patches</p>
<p>## TorchServe release 0.8.2 includes fixes to address the previously listed issue:</p>
<p>https://github.com/pytorch/serve/releases/tag/v0.8.2</p>
<p>**Tags for upgraded DLC release**
User can use the following new image tags to pull DLCs that ship with patched TorchServe version 0.8.2:
x86 GPU</p>
<p>* v1.9-pt-ec2-2.0.1-inf-gpu-py310
* v1.8-pt-sagemaker-2.0.1-inf-gpu-py310</p>
<p>x86 CPU</p>
<p>* v1.8-pt-ec2-2.0.1-inf-cpu-py310
* v1.7-pt-sagemaker-2.0.1-inf-cpu-py310</p>
<p>Graviton</p>
<p>* v1.7-pt-graviton-ec2-2.0.1-inf-cpu-py310
* v1.5-pt-graviton-sagemaker-2.0.1-inf-cpu-py310</p>
<p>Neuron</p>
<p>* 1.13.1-…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-8fxr-qfr9-p34w"/>
  </entry>
</feed>
