Bug 2427563 (CVE-2026-25211)

Summary: CVE-2026-25211 llamastack/llama-stack: Sensitive Information Exposure Through Log Files in Llama Stack PGVector Integration
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: jkoehler, lphiri, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A security issue was identified in the Llama Stack server when PGVector is used as a vector store provider. During initialization, the server logs print the PGVector database password in clear text. This occurs due to insufficient redaction of sensitive configuration fields. As a result, anyone with access to the application logs can retrieve database credentials, increasing the risk of unauthorized database access.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-01-07 12:01:07 UTC 
Sensitive information exposure vulnerability in the Llama Stack server when PGVector is configured as the vector store provider. The issue is caused by insecure logging of configuration parameters in the PGVector initialization routine, where the database password is written to server logs without redaction. When a LlamaStackDistribution is created, the plaintext password is printed at INFO log level. An attacker or unauthorized user with access to pod or application logs can obtain valid database credentials, potentially leading to unauthorized database access. This flaw does not require user interaction and can compromise the confidentiality of backend services relying on PGVector.