← Back
CVE-2025-55178
Vulnerability in llama-stack (CVE-2025-55178)
Summary
vulnerability in llama-stack (CVE-2025-55178). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.2.20` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-55178** has been found in llama-stack.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade llama-stack to **0.2.20** or later.
If unsure, ask your IT team or search "llama-stack CVE-2025-55178" on the vendor's site.
CVE-2025-55178 (llama-stack) — CWE-20 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `0.2.20` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-20) exists in llama-stack.
📍 Affected scope
llama-stack — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.2.20**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'llama-stack' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'llama-stack' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `llama-stack` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade llama-stack to 0.2.20ステージング環境で 0.2.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
llama-stack
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.20"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-55178
- advisory https://github.com/advisories/GHSA-x75h-m6jj-6cj2
- package https://github.com/llamastack/llama-stack
- package https://pypi.org/project/llama-stack
- web https://github.com/llamastack/llama-stack/pull/3281
- web https://github.com/llamastack/llama-stack/commit/efdb5558b8dcab4d141678bfed0a405e2f312b6f
- web https://github.com/llamastack/llama-stack/releases/tag/v0.2.20
- web https://www.facebook.com/security/advisories/cve-2025-55178