Skip to main content
VulnerabilityPublished Updated

CVE-2026-25211: llamastack Llama Stack · Sensitive Data in Logs

Affects llamastack Llama StackSource CVE Database V5

0

Not known to be exploited · CVSS 3.2 Low : upgrade to 0.4.0rc3 when convenient.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
3.2Low
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
llamastackLlama StackAffected
  • <0.4.0rc3
Fixed in
  • 0.4.0rc3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor and restrict access to log files containing initialization information to trusted personnel only, using strict file permissions and access controls.
  2. Implement log management solutions that support masking or redaction of sensitive information, ensuring that passwords and secrets are never logged in plaintext.
  3. If you cannot patch yet, consider disabling or modifying logging of initialization parameters in Llama Stack if possible.
  4. Use environment variables or secure vaults for managing credentials instead of hardcoding or passing them in ways that might be logged.
  5. Regularly audit logs for sensitive information exposure and remove or secure any logs containing passwords.
  6. Plan to upgrade Llama Stack to version 0.4.0rc3 or later once available, which addresses this vulnerability by censoring the password in logs.
  7. Employ host-based intrusion detection systems to alert on unauthorized access to log files.
  8. 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.

References

Community reviews

Loading reviews…