<Vulnerability name="CVE-2026-15574">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Moderate</ThreatSeverity>
    <PublicDate>2026-07-10T09:00:00</PublicDate>
    <Bugzilla id="2499594" url="https://bugzilla.redhat.com/show_bug.cgi?id=2499594" xml:lang="en:us">
vllm-orchestrator-gateway: vllm-orchestrator-gateway: Authorization header and full chat payloads logged at hard-coded DEBUG default
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>7.5</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-538</CWE>
    <Details xml:lang="en:us" source="Mitre">
A flaw was found in the vllm-orchestrator-gateway component. The system's production binary logs all incoming authorization headers and full chat payloads, which may contain personally identifiable information (PII) and secrets, to persistent logs. This sensitive data, including bearer tokens and chat content, can be accessed by any user with logging privileges. This vulnerability leads to information disclosure, potentially allowing an attacker to harvest credentials and sensitive conversation content.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in the vllm-orchestrator-gateway component. The system's production binary logs all incoming authorization headers and full chat payloads, which may contain personally identifiable information (PII) and secrets, to persistent logs. This sensitive data, including bearer tokens and chat content, can be accessed by any user with logging privileges. This vulnerability leads to information disclosure, potentially allowing an attacker to harvest credentials and sensitive conversation content.
    </Details>
    <Statement xml:lang="en:us">
This Moderate flaw in the vllm-orchestrator-gateway component causes sensitive data, including bearer tokens and chat payloads, to be logged at a DEBUG level by default. In Red Hat OpenShift environments, these logs are directed to the node journal and cluster logging stack, making them accessible to any user with `pods/log` RBAC within the namespace. This persistent logging of credentials and private conversation content poses a significant risk of information disclosure.
    </Statement>
    <Mitigation xml:lang="en:us">
To mitigate this issue, configure the `RUST_LOG` environment variable for the `vllm-orchestrator-gateway` component to a level higher than DEBUG, such as `INFO`. This will prevent the logging of sensitive authorization headers and full chat payloads to persistent logs. For example, set `RUST_LOG=info` in the deployment configuration. A restart of the affected pods or services is required for this change to take effect.
    </Mitigation>
    <PackageState cpe="cpe:/a:redhat:openshift_ai">
        <ProductName>Red Hat OpenShift AI (RHOAI)</ProductName>
        <FixState>Under investigation</FixState>
        <PackageName>rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-15574
https://nvd.nist.gov/vuln/detail/CVE-2026-15574
    </References>
</Vulnerability>