CVE-2026-78573: IBM ContextForge MCP Gateway default credentials auth bypass

CVE-2026-78573 · Severity: critical · CVSS 9.8 · Published 2026-09-10

IBM ContextForge MCP Gateway is a critical infrastructure component for managing model context protocol deployments. The gateway ships with hardcoded default credentials ("changeme") for administrative and API authentication that are only disabled if explicitly overridden. An attacker on the network can use these publicly known credentials to gain full administrative control of the gateway, compromising all connected systems and data.

Technologies: IBM Contextforge, IBM ContextForge MCP Gateway. Vendors: IBM.

Quick answers

Is CVE-2026-78573 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-78573 being exploited in the wild.
How severe is CVE-2026-78573?
Critical severity, with a CVSS score of 9.8, published 10 September 2026.
Which products and versions are affected?
IBM ContextForge MCP Gateway 1.0.0 through 1.0.9.
Is there a fix for CVE-2026-78573?
A patch was published on 2026-09-10: Fixed in version 1.0.10 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-78573 attacked?
It is attacked over the network.
Am I affected by CVE-2026-78573?
Check whether you run IBM Contextforge or IBM ContextForge MCP Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This is a use-of-default-credentials vulnerability (CWE-1392) in IBM ContextForge MCP Gateway. The product contains three password configuration fields (`platform_admin_password`, `default_user_password`, and `basic_auth_password`) that default to the publicly known value "changeme". When basic authentication or the administrative UI are enabled without explicitly setting strong passwords, the gateway accepts these default credentials and only issues a startup warning rather than enforcing a fail-closed posture. An unauthenticated remote attacker with network access to the gateway can login using these default credentials to gain full administrative access. The vulnerability affects versions 1.0.0 through 1.0.9; IBM recommends upgrading to version 1.0.10 and explicitly setting all three password fields to strong values. Workaround: Ensure `api_allow_basic_auth` and `mcpgateway_ui_enabled` remain disabled if upgrading is delayed.

Affected products

  • IBM ContextForge MCP Gateway 1.0.0 through 1.0.9

Timeline

  • 2026-09-10: disclosed
  • 2026-09-10: patched: Fixed in version 1.0.10

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.