CVE-2026-9073

MediumCVSS 6.2

Published: 23/06/2026(UTC)Updated: 15/07/2026(UTC)Translated: 16/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.15%

5th percentile - higher than 5% of all known CVEs

Summary

A flaw in foreman-mcp-server exposes sensitive authentication data through two logging mechanisms. Session identifiers and, when debug logging is enabled, authorization tokens and API keys are logged in cleartext.

Risk Assessment

The risk is a confidentiality breach as sensitive credentials are persisted in plain text in container logs, increasing exposure if logs are forwarded to a centralized platform.

Recommendation

Update foreman-mcp-server to a patched version immediately. Restrict log access and disable debug logging in production environments.

Other vulnerabilities in foreman-mcp-server

CVE-2026-12112High
A session management vulnerability was found in the foreman-mcp-server. An unauthenticated attacker can hijack active administrative sessions due to improper caching of authenticated connections, trusting a non-secret session ID without re-validating authentication tokens, and logging all newly created session IDs to standard logs. This issue can lead to privilege escalation and infrastructure-wide code execution.

Original NVD description (English source)

A flaw was found in foreman-mcp-server. This component utilizes two distinct logging mechanisms that can expose sensitive session and authentication data. One mechanism logs session identifiers, which are treated as authentication credentials, at an informational level. The other, when debug logging is enabled, incompletely sanitizes HTTP request headers, leading to the cleartext logging of sensitive information such as authorization tokens and API keys. This vulnerability can result in a confidentiality breach, as sensitive authentication data is persisted in plain text within container logs, increasing the risk if logs are forwarded to a centralized platform.