CVE Alert: CVE-2026-110278 – IBM

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.

**Risk verdict:** Treat this as a high-priority exposure risk and assess promptly; the supplied data does not establish KEV listing, active exploitation, PoC availability or EPSS, so urgency cannot be calibrated against those signals.

**Why this matters:** Misused identity claims could let an unauthorised party act with a user’s propagated identity, while disclosure could expose sensitive identity data to connected services. This risks unauthorised tool actions and downstream access, particularly where the gateway connects to systems holding business data or operational capabilities.

**Most likely attack path:** The network-reachable gateway requires no prior privileges or user action, but high attack complexity suggests an attacker needs a specific opportunity to capture and replay a valid signature. Scope is unchanged, so impact is primarily within the gateway’s security authority; downstream consequences depend on what connected MCP servers trust or permit that identity to do.

**Who is most exposed:** Organisations running the gateway with identity propagation enabled and connections to third-party or internally hosted MCP servers are most exposed, especially where those servers can access sensitive resources.

Look for repeated or anomalous identity-claim signatures across requests or sessions.

Review gateway and MCP-server logs for unexpected tool calls or identity mismatches.

Identify unusual disclosure or access of user identity data by connected servers.

Check gateway configuration and inventory identity-propagation status.

Mitigation and prioritisation:

Upgrade to the vendor’s fixed release; prioritise affected deployments.

If upgrade is delayed, disable identity propagation and restrict gateway access to trusted users.

Review connected servers’ permissions and revoke or rotate potentially exposed credentials or tokens.

Validate the upgrade and propagation settings in staging, then monitor closely after change.

Confirm KEV, exploitation, PoC and EPSS status before final prioritisation.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.