CVE-2026-9073: foreman-mcp-server Sensitive Information Exposure in Logs

foreman-mcp-server Updated 25 Sep 2026

Summary

23/06/2026
No i
Moderate
6.2

CVE-2026-9073: foreman-mcp-server Inserts Sensitive Information into Log File. Affects foreman-mcp-server versions < 0.4.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Foreman-mcp-server is a component designed for managing and orchestrating cloud infrastructure. It provides functionalities such as resource provisioning, monitoring, and management of virtual machines. However, it has been identified to have vulnerabilities related to logging mechanisms that can expose sensitive information, such as session identifiers and authentication tokens, if not properly managed.

Vulnerability Detail

A flaw exists in foreman-mcp-server where two logging mechanisms can inadvertently expose sensitive session and authentication data. One mechanism logs session identifiers at an informational level, while the other, when debug logging is enabled, fails to adequately sanitize HTTP request headers. This results in sensitive information, including authorization tokens and API keys, being logged in cleartext. The implications of this vulnerability are significant, as it can lead to unauthorized access and a breach of confidentiality, especially if logs are forwarded to centralized logging platforms.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, you can disable debug logging to prevent sensitive information from being logged. This can typically be done by adjusting the logging configuration in your application settings to set the log level to 'INFO' or higher, thus avoiding the logging of sensitive data.

Conclusion

The vulnerability CVE-2026-9073 in foreman-mcp-server poses a risk of exposing sensitive information through inadequate logging mechanisms. It is crucial to update to the latest version to mitigate this risk and ensure the confidentiality of authentication data.

See every vulnerability recorded for foreman-mcp-server →

Share this vulnerability

FAQ

CVE-2026-9073 is a vulnerability in foreman-mcp-server that allows sensitive information, such as session identifiers and authentication tokens, to be logged in cleartext.

If your application uses foreman-mcp-server and logs sensitive information, it may expose this data to unauthorized users, leading to potential security breaches.

You should update foreman-mcp-server to a version higher than 0.4.2 to mitigate the risk associated with this vulnerability.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software without needing to access the code. Visit https://vulert.com for more information.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback