CVE-2026-110278

IBM ContextForge MCP Gateway is affected by an information exposure vulnerability

  • High 7.4

Description

IBM ContextForge MCP Gateway 1.0.0 through 1.1.0 could allow an attacker to replay identity propagation claims signatures or expose sensitive user identity information to third-party MCP servers due to static signature payloads and missing per-gateway configuration checks during tool invocation.

Key facts

Published
13 Nov 2026
Last changed
13 Nov 2026
Assigned by
ibm
EPSS
0.243% likely to be exploited in the next 30 days, higher than 15.637% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.4CVSS 3.1, Highfrom the CNA (ibm)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

What to do

  • IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway v1.0.0-v1.1.0Upgrade to v1.1.1 immediately [ Release notes https://github.com/IBM/mcp-context-forge/releases/tag/v1.1.1 ]CNA solution statement
  • IBM strongly recommends upgrading to the fixed version. If you cannot update disable identity propagation globally (set `IDENTITY_PROPAGATION_ENABLED=false`) so that no upstream MCP server receives user identity information, and restrict access to the gateway to trusted users.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
IBMContextForge MCP Gateway
  • 1.0.0 up to and including 1.1.0 (affected)

Timeline

  1. 13 Nov 2026 Published

Weakness

References