CVE-2026-9073

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreHIGH confidence

Score 6.2 from GitHub Security Advisory published 2026-06-23. a secondary CVSS source baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.2Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.2
EG Score
6.2(high)
EPSS
4.7%
KEV
Not listed

Published

June 23, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jun 24, 2026
Patch available. Sources: redhat.
redhat

2480151 – (CVE-2026-9073) CVE-2026-9073 foreman-mcp-server: MCP Server: Insecure Sensitive HTTP Header Sanitization

https://bugzilla.redhat.com/show_bug.cgi?id=2480151
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-9073

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsatellite/foreman-mcp-server-rhel9:17822286922026-06-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 14:06 UTCEG score recompute
  3. 2026-07-06 14:06 UTCVendor advisory
  4. 2026-07-06 14:05 UTCGHSA enrichment
  5. 2026-07-05 14:45 UTCEG score recompute
  6. 2026-07-05 14:45 UTCVendor advisory
  7. 2026-07-05 14:45 UTCGHSA enrichment
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 15:21 UTCEG score recompute
  11. 2026-07-04 15:21 UTCVendor advisory
  12. 2026-07-04 15:21 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 15:58 UTCEG score recompute
  16. 2026-07-03 15:58 UTCVendor advisory
  17. 2026-07-03 15:58 UTCGHSA enrichment
  18. 2026-07-02 16:36 UTCEG score recompute
  19. 2026-07-02 16:36 UTCVendor advisory
  20. 2026-07-02 16:36 UTCGHSA enrichment
  21. 2026-07-01 17:14 UTCEG score recompute
  22. 2026-07-01 17:14 UTCVendor advisory
  23. 2026-07-01 17:13 UTCGHSA enrichment
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 29 more
  1. 2026-06-30 17:48 UTCEG score recompute
  2. 2026-06-30 17:48 UTCVendor advisory
  3. 2026-06-30 17:48 UTCGHSA enrichment
  4. 2026-06-29 18:28 UTCEG score recompute
  5. 2026-06-29 18:28 UTCVendor advisory
  6. 2026-06-29 18:28 UTCGHSA enrichment
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 19:09 UTCEG score recompute
  9. 2026-06-28 19:09 UTCVendor advisory
  10. 2026-06-28 19:09 UTCGHSA enrichment
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 19:49 UTCEG score recompute
  14. 2026-06-27 19:49 UTCVendor advisory
  15. 2026-06-27 19:49 UTCGHSA enrichment
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-26 20:29 UTCEG score recompute
  18. 2026-06-26 20:29 UTCVendor advisory
  19. 2026-06-26 20:29 UTCGHSA enrichment
  20. 2026-06-25 21:10 UTCEG score recompute
  21. 2026-06-25 21:10 UTCVendor advisory
  22. 2026-06-25 21:10 UTCGHSA enrichment
  23. 2026-06-25 13:50 UTCEPSS rescore
  24. 2026-06-24 21:50 UTCEG score recompute
  25. 2026-06-24 21:50 UTCVendor advisory
  26. 2026-06-24 21:50 UTCGHSA enrichment
  27. 2026-06-24 14:05 UTCEPSS rescore
  28. 2026-06-23 22:30 UTCEG score recompute
  29. 2026-06-23 22:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-9073?
CVE-2026-9073 is a medium vulnerability published on June 23, 2026. 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…
When was CVE-2026-9073 disclosed?
CVE-2026-9073 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9073 actively exploited?
CVE-2026-9073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9073?
CVE-2026-9073 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-9073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9073

Explore →

Is Your Infrastructure Affected by CVE-2026-9073?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.