High [CVE-2026-15574] Authorization header and full chat payloads logged at hard-coded DEBUG default
This high-severity Red Hat Linux advisory covers CVE-2026-15574 affecting Red Hat OpenShift AI 2.25, Red Hat OpenShift AI 3.4.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
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.
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.
Red Hat severity: Moderate — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Weakness: CWE-538.
Affected Red Hat products: Red Hat OpenShift AI 2.25; Red Hat OpenShift AI 3.4. Red Hat fixing advisory: RHSA-2026:87410, RHSA-2026:84734.
Is CVE-2026-15574 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-15574 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-15574?
Upgrade to a fixed release named by Red Hat:
- rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9:1790929477
- rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9:1791363252
- RHSA-2026:87410
- RHSA-2026:84734
Confirm against the vendor advisory before you patch.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
- rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9:1790929477
- rhoai/odh-trustyai-vllm-orchestrator-gateway-rhel9:1791363252
- RHSA-2026:87410
- RHSA-2026:84734
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 5 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-42271May 8, 2026Authenticated command execution via MCP stdio test endpoints
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
- CVE-2026-48710May 26, 2026Security restriction bypass via malformed HTTP Host header
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.