<?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-02T17:16:23.838568+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/euvd-2026-137940</id>
    <title>EUVD-2026-137940</title>
    <updated>2026-10-02T17:16:23.904947+00:00</updated>
    <content>EUVD-2026-137940</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-137940"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-35199</id>
    <title>fkie_cve-2024-35199</title>
    <updated>2026-10-02T17:16:23.904982+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>TorchServe is a flexible and easy-to-use tool for serving and scaling PyTorch models in production. In affected versions the two gRPC ports 7070 and 7071, are not bound to [localhost](http://localhost/) by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected. This issue in TorchServe has been fixed in PR #3083. TorchServe release 0.11.0 includes the fix to address this vulnerability. Users are advised to upgrade. There are no known workarounds for this vulnerability.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-35199"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hhpg-v63p-wp7w</id>
    <title>GHSA-hhpg-v63p-wp7w — TorchServe gRPC Port Exposure</title>
    <updated>2026-10-02T17:16:23.905017+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: torchserve</p>
<p>### Impact
The two gRPC ports 7070 and 7071, are not bound to [localhost](http://localhost/) by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.</p>
<p>### Patches
This issue in TorchServe has been fixed in [#3083](https://github.com/pytorch/serve/pull/3083).</p>
<p>TorchServe release 0.11.0 includes the fix to address this vulnerability.</p>
<p>### References
* [#3083](https://github.com/pytorch/serve/pull/3083)
* [TorchServe release v0.11.0](https://github.com/pytorch/serve/releases/tag/v0.11.0)</p>
<p>Thank Kroll Cyber Risk for for responsibly disclosing this issue.</p>
<p>If you have any questions or comments about this advisory, we ask that you contact AWS Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hhpg-v63p-wp7w"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-1971</id>
    <title>PYSEC-2026-1971 — TorchServe gRPC Port Exposure</title>
    <updated>2026-10-02T17:16:23.905051+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: torchserve</p>
<p>### Impact
The two gRPC ports 7070 and 7071, are not bound to [localhost](http://localhost/) by default, so when TorchServe is launched, these two interfaces are bound to all interfaces. Customers using PyTorch inference Deep Learning Containers (DLC) through Amazon SageMaker and EKS are not affected.</p>
<p>### Patches
This issue in TorchServe has been fixed in [#3083](https://github.com/pytorch/serve/pull/3083).</p>
<p>TorchServe release 0.11.0 includes the fix to address this vulnerability.</p>
<p>### References
* [#3083](https://github.com/pytorch/serve/pull/3083)
* [TorchServe release v0.11.0](https://github.com/pytorch/serve/releases/tag/v0.11.0)</p>
<p>Thank Kroll Cyber Risk for for responsibly disclosing this issue.</p>
<p>If you have any questions or comments about this advisory, we ask that you contact AWS Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-1971"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1687</id>
    <title>WID-SEC-W-2024-1687 — PyTorch: Mehrere Schwachstellen</title>
    <updated>2026-10-02T17:16:23.905079+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter anonymer Angreifer kann mehrere Schwachstellen in PyTorch ausnutzen, um Sicherheitsmaßnahmen zu umgehen oder einen unspezifischen Angriff durchzuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1687"/>
  </entry>
</feed>
