VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

torchserve: vulnerability history, versions and safety

torchserve is a package in the PyPI ecosystem. Vulert records 11 vulnerabilities for it across 25 releases, from Oct 2023 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded C3 H1 M2 U5
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all torchserve vulnerabilities

Vulert verdict on torchserve 0.12.0 i

Updated on 23 Oct 2026

Careful: 0.12.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.12.0 — affected i
  • Vulnerabilities on record 11 over 2 years · 5 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 2 i
  • Depended on by 6 packages i
  • Stars 4,345 i
  • OpenSSF scorecard 4/10 i
  • Last release 24 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for torchserve, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.12.0 30 Sep 2024 M1 U1 Apache-2.0 No Details →
0.11.1 18 Jul 2024 M1 U1 Apache-2.0 No Details →
0.11.0 16 May 2024 M1 U1 Apache-2.0 No Details →
0.10.0 14 Mar 2024 C1 H1 M1 U3 Apache-2.0 No Details →
0.9.0 12 Oct 2023 C1 H1 M1 U3 Apache-2.0 No Details →
0.8.2 28 Aug 2023 C1 H1 M2 U4 Apache-2.0 No Details →
0.8.1 14 Jun 2023 C3 H1 M2 U5 Apache-2.0 No Details →
0.8.0 11 May 2023 C3 H1 M2 U5 Apache-2.0 No Details →
0.7.1 08 Feb 2023 C3 H1 M2 U5 Apache-2.0 No Details →
0.7.0 12 Dec 2022 C3 H1 M2 U5 Apache-2.0 No Details →
0.6.1 14 Nov 2022 C3 H1 M2 U5 Apache-2.0 No Details →
0.6.0 13 May 2022 C3 H1 M2 U5 Apache-2.0 No Details →
0.5.3 01 Mar 2022 C3 H1 M2 U5 Apache-2.0 No Details →
0.5.2 29 Dec 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.5.1 16 Dec 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.5.0 19 Nov 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.4.2 02 Aug 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.4.1 22 Jul 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.4.0 20 May 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.3.1 15 Mar 2021 C3 H1 M2 U5 Apache-2.0 No Details →
0.3.0 17 Dec 2020 C3 H1 M2 U5 Apache-2.0 No Details →
0.2.2 14 Dec 2020 C2 M2 U4 Apache-2.0 No Details →
0.2.0 11 Aug 2020 C2 M2 U4 Apache-2.0 No Details →
0.1.1 09 Jun 2020 C2 M2 U4 Apache-2.0 No Details →
0.0.1b20200409 21 Apr 2020 C1 M1 U2 Apache-2.0 No Details →

All 25 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 3
  • 2024 2
  • 2025 1
  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for torchserve

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
TorchServe Pre-Auth Remote Code Execution in torchserve 9.9 critical 0.8.2 02 Oct 2023
CVE-2023-43654: TorchServe Server-Side Request Forgery vulnerability in torchserve 9.8 critical 0.8.2 02 Oct 2023
CVE-2024-35198: TorchServe vulnerable to bypass of allowed_urls configuration 9.8 critical 0.11.0 18 Jul 2024
CVE-2023-43654: TorchServe Server-Side Request Forgery Vulnerability 9.8 critical 0.8.2 29 Jun 2026
CVE-2024-35198: TorchServe Bypass of Allowed URLs Configuration Vulnerability 9.8 critical 0.11.0 29 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About torchserve

Is torchserve safe to use?

Vulert records 11 vulnerabilities for torchserve in PyPI: 3 critical, 1 high, 2 medium and 0 low, plus 5 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is torchserve's Vulert package health score?

Vulert scores torchserve 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of torchserve affected?

Yes. 0.12.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of torchserve should I use?

0.12.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does torchserve have?

11 vulnerabilities are recorded for torchserve in the PyPI ecosystem: 3 critical, 1 high, 2 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new torchserve vulnerabilities disclosed?

5 vulnerabilities were recorded for torchserve in the last 12 months, and the oldest entry in this database dates to 02 Oct 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of torchserve are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor torchserve for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the torchserve version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.