dbcve.org
SatelliteApplication · Redhat

CVE-2026-9073

MEDIUM · 6.2 CVSS v3.1 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The foreman-mcp-server component has two logging vulnerabilities: (1) session identifiers are logged at informational level despite being authentication credentials, and (2) debug logging incompletely sanitizes HTTP request headers, allowing authorization tokens and API keys to be logged in cleartext. This exposes sensitive authentication data in container logs.

MitigationDisable debug logging in production environments and implement proper sanitization filters for session identifiers, authorization tokens, and API keys in all logging paths to prevent sensitive data from being persisted in plain text.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SatelliteApplication
Affected:= 6.19
ForemanApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if foreman-mcp-server component is in use
    Check running processes or installed packages for foreman-mcp-server. On RHEL/Satellite: rpm -qa | grep foreman-mcp-server or systemctl list-units | grep foreman-mcp-server. On Foreman: check the /opt/foreman directory or ps aux for mcp-server processes.
    Affected if The foreman-mcp-server component is installed and running in the environment.
  2. Determine the configured logging level
    Inspect the foreman-mcp-server configuration file (typically /etc/foreman-mcp-server/settings.yaml or similar) and look for log_level, log_level_debug, or similar settings. Also check environment variables like LOG_LEVEL or DEBUG.
    Affected if Debug logging is explicitly enabled or the log level is set to debug/DEBUG.
  3. Locate and inspect foreman-mcp-server log files
    Find the log directory - typically /var/log/foreman-mcp-server/, /var/log/foreman/, or check journalctl -u foreman-mcp-server. Review recent log entries for patterns matching session identifiers, authorization headers, or API keys.
    Affected if Logs contain visible session identifiers (look for sid=, session, or alphanumeric tokens after 'session') or authorization tokens (Bearer, API-Key, Token patterns in cleartext).
  4. Review HTTP header logging behavior
    Enable debug logging temporarily in a non-production test environment and send requests with custom Authorization or X-API-Key headers. Capture the resulting log output and verify if these headers appear in plain text.
    Affected if Authorization tokens or API keys sent in HTTP request headers appear in cleartext in debug logs.
  5. Check for sanitization filters in logging configuration
    Search the foreman-mcp-server configuration and source code (if accessible) for regex patterns, filters, or sanitization logic that handles sensitive headers like Authorization, Cookie, X-API-Key, or session identifiers before logging.
    Affected if No sanitization filters are defined for authentication credentials, or filters exist but do not cover session identifiers, authorization tokens, and API keys.

A user is affected if foreman-mcp-server is running with debug logging enabled and sensitive authentication data (session IDs, authorization tokens, or API keys) can be observed in plain text within log files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable debug logging in production environments and implement proper sanitization filters for session identifiers, authorization tokens, and API keys in all logging paths to prevent sensitive data from being persisted in plain text.

Fix this in Satellite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9073 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data