VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

llama-stack: vulnerability history, versions and safety

llama-stack is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 90 releases, from Sep 2025 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
4 vulnerabilities recorded M1 L1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 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 llama-stack vulnerabilities

Vulert verdict on llama-stack 0.7.3 i

Updated on 23 Oct 2026

Good news: 0.7.3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 0.7.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.7.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.7.3 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 8,441 i
  • Last release 2 months ago i
  • Licence MIT 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 llama-stack, 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.7.3 27 Jul 2026 none MIT — Details →
0.4.7 27 Jul 2026 none MIT — Details →
0.5.4 26 Jun 2026 none MIT — Details →
0.5.3 26 Jun 2026 none MIT — Details →
0.4.6 29 May 2026 none MIT — Details →
0.7.2 28 May 2026 none MIT — Details →
0.7.1 08 Apr 2026 none MIT — Details →
0.7.0 01 Apr 2026 none MIT — Details →
0.6.1 30 Mar 2026 none MIT — Details →
0.6.0 11 Mar 2026 none MIT — Details →
0.5.2 06 Mar 2026 none MIT — Details →
0.5.1 19 Feb 2026 none MIT — Details →
0.4.5 19 Feb 2026 none MIT — Details →
0.5.0 05 Feb 2026 none MIT — Details →
0.5.0rc1 04 Feb 2026 none MIT — Details →
0.4.4 30 Jan 2026 none MIT — Details →
0.4.3 26 Jan 2026 L1 U1 MIT Yes Details →
0.4.2 16 Jan 2026 L1 U1 MIT Yes Details →
0.4.1 13 Jan 2026 L1 U1 MIT Yes Details →
0.4.0 06 Jan 2026 L1 U1 MIT Yes Details →
0.3.5 15 Dec 2025 L1 U1 MIT Yes Details →
0.3.4 03 Dec 2025 L1 U1 MIT Yes Details →
0.3.3 24 Nov 2025 L1 U1 MIT Yes Details →
0.3.2 12 Nov 2025 L1 U1 MIT Yes Details →
0.2.24 12 Nov 2025 L1 U1 MIT Yes Details →
0.3.1 31 Oct 2025 L1 U1 MIT Yes Details →
0.3.0 21 Oct 2025 L1 U1 MIT Yes Details →
0.2.23 26 Sep 2025 L1 U1 MIT Yes Details →
0.2.22 16 Sep 2025 L1 U1 MIT Yes Details →
0.2.21 08 Sep 2025 L1 U1 MIT Yes Details →
0.2.20 29 Aug 2025 L1 U1 MIT Yes Details →
0.2.19 26 Aug 2025 M1 L1 U2 MIT Yes Details →
0.2.18 19 Aug 2025 M1 L1 U2 MIT Yes Details →
0.2.17 05 Aug 2025 M1 L1 U2 MIT Yes Details →
0.2.16 28 Jul 2025 M1 L1 U2 MIT Yes Details →
0.2.15 15 Jul 2025 M1 L1 U2 MIT Yes Details →
0.2.14 04 Jul 2025 M1 L1 U2 MIT Yes Details →
0.2.13 27 Jun 2025 M1 L1 U2 MIT Yes Details →
0.2.12 20 Jun 2025 M1 L1 U2 MIT Yes Details →
0.2.11 17 Jun 2025 M1 L1 U2 MIT Yes Details →
0.2.10.1 06 Jun 2025 M1 L1 U2 MIT Yes Details →
0.2.10 05 Jun 2025 M1 L1 U2 MIT Yes Details →
0.2.9 30 May 2025 M1 L1 U2 MIT Yes Details →
0.2.8 27 May 2025 M1 L1 U2 MIT Yes Details →
0.2.7 16 May 2025 M1 L1 U2 MIT Yes Details →
0.2.6 12 May 2025 M1 L1 U2 MIT Yes Details →
0.2.5 03 May 2025 M1 L1 U2 MIT Yes Details →
0.2.4 29 Apr 2025 M1 L1 U2 MIT Yes Details →
0.2.3 25 Apr 2025 M1 L1 U2 MIT Yes Details →
0.2.2 13 Apr 2025 M1 L1 U2 MIT Yes Details →
0.2.1 05 Apr 2025 M1 L1 U2 MIT Yes Details →
0.2.0 05 Apr 2025 M1 L1 U2 MIT Yes Details →
0.1.9 29 Mar 2025 M1 L1 U2 MIT Yes Details →
0.1.8 23 Mar 2025 M1 L1 U2 MIT Yes Details →
0.1.7 14 Mar 2025 M1 L1 U2 MIT Yes Details →
0.1.6 08 Mar 2025 M1 L1 U2 MIT Yes Details →
0.1.5.1 28 Feb 2025 M1 L1 U2 MIT Yes Details →
0.1.5 28 Feb 2025 M1 L1 U2 MIT Yes Details →
0.1.4 24 Feb 2025 M1 L1 U2 MIT Yes Details →
0.1.3 14 Feb 2025 M1 L1 U2 MIT Yes Details →
0.1.2 07 Feb 2025 M1 L1 U2 MIT Yes Details →
0.1.1 02 Feb 2025 M1 L1 U2 MIT Yes Details →
0.1.0 24 Jan 2025 M1 L1 U2 MIT Yes Details →
0.0.63 18 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.62 18 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.61 10 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.60 10 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.59 10 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.58 06 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.57 03 Dec 2024 M1 L1 U2 MIT Yes Details →
0.0.56 30 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.55 23 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.54 22 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.53 20 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.52 09 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.51.dev0 09 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.51.0 09 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.51 09 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.50 09 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.49 05 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.48 05 Nov 2024 M1 L1 U2 MIT Yes Details →
0.0.47 28 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.46 25 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.45 24 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.44 24 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.43 22 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.42 14 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.41 10 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.40 04 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.39 03 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.38 03 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.37 02 Oct 2024 M1 L1 U2 MIT Yes Details →
0.0.36 25 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.35 25 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.24 24 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.23 24 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.21 23 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.20 19 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.19 18 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.18 18 Sep 2024 M1 L1 U2 MIT Yes Details →
0.0.1a5 13 Sep 2024 M1 L1 U2 — Yes Details →
0.0.1a4 12 Sep 2024 M1 L1 U2 — Yes Details →
0.0.1a3 12 Sep 2024 M1 L1 U2 — Yes Details →
0.0.1a2 11 Sep 2024 M1 L1 U2 — Yes Details →
0.0.1a1 10 Sep 2024 M1 L1 U2 — Yes Details →
0.0.1a0 10 Sep 2024 M1 L1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for llama-stack

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-55178: Llama Stack Remote Code Execution Vulnerability 5.3 medium 0.2.20 24 Sep 2025
CVE-2025-55178: Llama Stack Remote Code Execution Vulnerability 5.3 medium 0.2.20 07 Jul 2026
CVE-2026-25211: Llama Stack Exposes Secret in Initialization Log 3.2 low 0.4.4 30 Jan 2026
CVE-2026-25211: Llama Stack Exposes Secret in Initialization Log 3.2 low 0.4.4 07 Jul 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 llama-stack

Is llama-stack safe to use?

Vulert records 4 vulnerabilities for llama-stack in PyPI: 0 critical, 0 high, 1 medium and 1 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is llama-stack's Vulert package health score?

Vulert scores llama-stack 85/100, which reads as healthy. 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).

Is the latest version of llama-stack affected?

No. 0.7.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of llama-stack should I use?

0.7.3 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 llama-stack have?

4 vulnerabilities are recorded for llama-stack in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 1 low, plus 2 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 llama-stack vulnerabilities disclosed?

3 vulnerabilities were recorded for llama-stack in the last 12 months, and the oldest entry in this database dates to 24 Sep 2025. 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 llama-stack 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 llama-stack for upcoming vulnerabilities?

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