CVE-2026-25211: llamastack Llama Stack · Sensitive Data in Logs
Affects llamastack Llama StackSource CVE Database V5
Not known to be exploited · CVSS 3.2 Low : upgrade to 0.4.0rc3 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.4.0rc3
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade llamastack Llama Stack to 0.4.0rc3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| llamastackLlama Stack | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Monitor and restrict access to log files containing initialization information to trusted personnel only, using strict file permissions and access controls.
- Implement log management solutions that support masking or redaction of sensitive information, ensuring that passwords and secrets are never logged in plaintext.
- If you cannot patch yet, consider disabling or modifying logging of initialization parameters in Llama Stack if possible.
- Use environment variables or secure vaults for managing credentials instead of hardcoding or passing them in ways that might be logged.
- Regularly audit logs for sensitive information exposure and remove or secure any logs containing passwords.
- Plan to upgrade Llama Stack to version 0.4.0rc3 or later once available, which addresses this vulnerability by censoring the password in logs.
- Employ host-based intrusion detection systems to alert on unauthorized access to log files.
- Educate developers and system administrators about secure logging practices to prevent similar issues in the future.
Description
Llama Stack (aka llama-stack) before 0.4.0rc3 does not censor the pgvector password in the initialization log.