CVE-2026-25211 is a low-severity (CVSS 3.2) CWE-532 vulnerability in llama-stack. A fix is available for llama-stack — see the affected versions and patch details below.
Llama Stack exposes secret in initialization log
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25211.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
llama-stackReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Llama Stack (aka llama-stack) before 0.4.0rc3 does not censor the pgvector password in the initialization log.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | llama-stack | all versions | 0.4.4pip install --upgrade 'llama-stack==0.4.4' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for llama-stack, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update llama-stack to 0.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25211 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The vulnerability has a Low impact.The flaw involves information exposure through log files in the Llama Stack server when PGVector is configured, where database passwords are logged in plaintext.
To mitigate this issue, ensure strict access controls are implemented for server and application logs associated with Llama Stack deployments. Restrict log file and directory access to authorized personnel only to prevent unauthorized disclosure of sensitive database credentials. Consider integrating log redaction or encryption solutions if supported by your logging infrastructure for enhanced data protection.Source: Red Hat security advisory for CVE-2026-25211 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-25211 in your dependencies?
Find it across PyPI, including transitive dependencies.