CVE-2026-77822IBM ContextForge MCP Gateway is affected by server-side request forgery (DNS rebinding) via the A2A agent invocation endpoint
- 8.2HighCVSS base score
- 0.37%Exploitation in 30 daysEPSS · top 69% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
IBM ContextForge MCP Gateway could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery via DNS rebinding.
Timeline
ID reserved
By ibm
- 14 days later
· 14 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| ibmCNA (assigner) | 3.1 | High8.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N |
| NVDNVD · Analyzed | 3.1 | Critical9.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.37% · top 69% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.
Affected products
IBM · ContextForge MCP Gateway
- affected <= v1.0.8
What to do
Solution: IBM strongly recommends addressing the vulnerability now. Product(s)Version(s) number and/or range Remediation/Fix/InstructionsIBM ContextForge MCP Gateway<= v1.0.8Upgrade to v1.0.9 https://github.com/IBM/mcp-context-forge/releases/tag/v1.0.9 Note: <Component A / B names> are bundled with <Product profile name> to provide <feature / function description>
Workaround: Operators who cannot immediately upgrade can reduce exposure by: 1. **Disable A2A** — set the environment variable `MCPGATEWAY_A2A_ENABLED=False` to disable the A2A subsystem entirely. This removes the vulnerable endpoint from the attack surface at the cost of A2A functionality. 2. **Restrict A2A create/invoke permissions** — revoke A2A creation and invocation rights from developer and team_admin roles in environments where A2A is not required. 3. **Network-level egress controls** — enforce outbound network policy at the host or cloud level to block the gateway process from reaching cloud metadata endpoints and private RFC 1918 address ranges, preventing exploitation of the DNS-rebinding window even if a rebind attempt succeeds. None of these mitigations eliminate the underlying vulnerability; IBM strongly recommends upgrading to the fixed version.
References
References1
- https://www.ibm.com/support/pages/node/7286055 (opens in a new tab)vendor-advisorypatch
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71256 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-77822)Record last updated .