Public vulnerability disclosure

CVE-2026-110278

IBM ContextForge MCP Gateway is affected by an information exposure vulnerability

publishedCWE-294

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.

Technical severity7.4 highCVSS 3.1 · CNA: ibm
Published2026-11-13Source updated 2026-11-13
Collected2026-11-131 attributed source

Fixes and workarounds

Fix

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 ]

Source: CNA: ibm

Workaround

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.

Source: CNA: ibm

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: ibm

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
ContextForge MCP Gateway
IBM
≥ 1.0.0; ≤ 1.1.0 (affected, semver) CNA: ibm

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.4
high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NCNA: ibm

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide