MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

IBM's ContextForge MCP Gateway draws six CVE records in ten days, one critical default-credentials bug already patched and one SSRF report closed by documentation alone

IBM's own CNA published five CVE records against ContextForge MCP Gateway between 2026-09-04 and 2026-09-10, and GitHub's CNA published a sixth against the same repository on 2026-09-14. The critical record, CVE-2026-78573, is a hardcoded "changeme" default across three password settings; IBM's support page names v1.0.10, not the v1.0.8 the CVE text's own truncated version range would imply, as the actual fix, released 2026-09-07. Four more IBM-track records cover SSRF and credential-handling bugs with shipped fixes, except CVE-2026-18489, which IBM's text says was closed by a documentation change with no code fix. GitHub's separate record covers a DNS TOCTOU SSRF bypass fixed three months before it was published.

IBM's own CNA published five CVE records against ContextForge MCP Gateway between 2026-09-04 and 2026-09-10, and GitHub's separate CNA published a sixth against the same repository on 2026-09-14. Neither is cataloged here as an entity.

The critical record is CVE-2026-78573, CVSS 3.1 9.8, a hardcoded default credential of "changeme" across three password settings (platform_admin_password, default_user_password, basic_auth_password). When an operator enables basic authentication or the admin UI without setting these explicitly, the gateway accepts the known default and only logs a startup warning rather than refusing to start. The CVE record's own truncated version field names the affected range as ending at v1.0.7, but IBM's support page states the actual affected range runs through v1.0.9 and names v1.0.10, released 2026-09-07, three days before the record published on 2026-09-10, as the fix.

Four more IBM-track records follow, three with shipped fixes and one without. CVE-2026-18486 (high, 8.8) let an authenticated developer supply a jq filter that executed unrestricted builtins such as $ENV, exposing environment variables including cryptographic keys and database credentials; fixed in v1.0.8, released 2026-08-18. CVE-2026-77822 (high, 8.2) is a DNS-rebinding SSRF in the A2A agent invocation endpoint, the only outbound path in the gateway that did not pin the resolved IP at connection time; fixed in v1.0.9, released 2026-09-01. CVE-2026-18905 (high, 7.7) is a DNS TOCTOU SSRF at tool invocation, where a registered tool's URL is trusted without re-validation after registration; IBM's page dates the fixing merge to 2026-07-29, and the release, v1.0.7, followed on 2026-08-05. CVE-2026-18489 (high, 7.4), by contrast, has no code fix at all: IBM's page states the affected Translate utility "is intended only for local, single-session development use" and that a pull request merged 2026-08-24 only updated the documentation to make that restriction explicit, not the code.

Separately, GitHub's CNA published CVE-2026-53708 against the same repository on 2026-09-14, the latest date in this batch. It describes a DNS TOCTOU race condition that bypasses SSRF protection at the /admin/gateways/test endpoint, rated medium at CVSS 3.1 6.6. The fix, v1.0.3, was released 2026-06-10, the same day the CVE was reserved but three months before GitHub published the record.

How was this verified, and what are the sources?

Published · last verified · confidence 1.00.

  1. IBM Security Bulletin (node/7286834), CVE-2026-78573 - "IBM ContextForge MCP Gateway v1.0.0 - v1.0.9 ... Upgrade to v1.0.10"; CVSS 3.1 9.8 critical, IBM-scored; mechanism "three password configuration fields ... ship with the publicly known default value 'changeme'" - accessed
  2. CVE-2026-78573 CNA record (ibm) - datePublished 2026-09-10T21:42:36Z, dateReserved 2026-08-24T20:35:05Z, affected "1.0.0" through "1.0.7" in the CNA's own truncated version field (IBM's support page corrects this to v1.0.9 as the last affected release) - accessed
  3. IBM/mcp-context-forge releases - v1.0.10 published 2026-09-07T18:57:08Z, v1.0.9 2026-09-01T14:23:58Z, v1.0.8 2026-08-18T13:14:39Z, v1.0.7 2026-08-05T18:07:27Z, v1.0.3 2026-06-10T10:45:40Z - accessed
  4. IBM Security Bulletin (node/7286052), CVE-2026-18486 - "<=v1.0.7 Upgrade to v1.0.8"; CVSS 3.1 8.8 high; mechanism "a jq program in the tool jsonpath_filter field that executes unrestricted built-ins such as $ENV ... exposing environment variables including cryptographic keys and database credentials" - accessed
  5. IBM Security Bulletin (node/7286056), CVE-2026-18489 - "The IBM ContextForge Translate service is intended only for local, single-session development use ... PR #6388 (merged 2026-08-24) updates the product documentation to make this restriction explicit", no version bump or code fix named; CVSS 3.1 7.4 high - accessed
  6. IBM Security Bulletin (node/7286055), CVE-2026-77822 - "<=v1.0.8 Upgrade to v1.0.9"; CVSS 3.1 8.2 high; mechanism "the A2A invocation path does not pin the DNS-resolved IP address at connection time, allowing ... a classic DNS-rebinding attack" - accessed
  7. IBM Security Bulletin (node/7286053), CVE-2026-18905 - "<=v1.0.6 Upgrade to v1.0.7 or higher ... Fix merged: 2026-07-29"; CVSS 3.1 7.7 high; mechanism "the stored URL is used directly without re-validation or DNS-resolution pinning" at tool invocation - accessed
  8. GHSA-9hgc-g3w5-67cm / CVE-2026-53708 (GitHub_M CNA) on IBM/mcp-context-forge - "DNS TOCTOU race condition causes SSRF protection bypass (/admin/gateways/test)"; CVSS 3.1 6.6 medium; fixed in v1.0.3, released 2026-06-10, the same day the CVE was reserved but three months before the record published 2026-09-14 - accessed

← All news