# CVE-2026-9073: Foreman-mcp-server: mcp server: insecure sensitive http header sanitization

> Attackers with log access can retrieve sensitive authentication tokens and API keys due to insecure logging practices in the Foreman MCP server.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-7rcj-2493-83x3, PYSEC-2026-4050

## What is CVE-2026-9073?

CVE-2026-9073 is a medium-severity vulnerability in Redhat Satellite, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-9073?

3 open source packages ship an affected version, including foreman-mcp-server. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `foreman-mcp-server` | PyPI | All versions to 0.4.2 | None |
| `foreman-mcp-server` | PyPI | All versions to 0.4.2 | None |
| `foreman-mcp-server` | PyPI | All versions to 0.4.2 | None |

Products: Redhat Satellite, Theforeman Foreman.

## How do I fix CVE-2026-9073?

No fix has been published for CVE-2026-9073 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9073 being exploited?

There is no known exploitation of CVE-2026-9073 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Satellite

- [CVE-2024-7012](https://insights.sbomify.com/CVE-2024-7012/): Puppet-foreman: an authentication bypass vulnerability exists in foreman (critical 9.8)
- [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8)
- [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1)
- [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1)
- [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9073 and fix it if it is affected.

What it is: CVE-2026-9073 is a medium-severity vulnerability in Redhat Satellite, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9073 in the wild and no public exploit code.

Affected packages and fixed versions:
- foreman-mcp-server (PyPI): affected all versions up to 0.4.2; no fix listed
- foreman-mcp-server (PyPI): affected all versions up to 0.4.2; no fix listed
- foreman-mcp-server (PyPI): affected all versions up to 0.4.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9073/ (Markdown: https://insights.sbomify.com/CVE-2026-9073/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9073
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9073
- OSV: https://osv.dev/vulnerability/CVE-2026-9073

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9073/
Summaries are generated and may contain mistakes; the official description above is the record.