Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-77822IBM ContextForge MCP Gateway is affected by server-side request forgery (DNS rebinding) via the A2A agent invocation endpoint

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

  1. ID reserved

    By ibm

  2. · 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

CVSS scores of CVE-2026-77822, by who scored it
Scored byCVSSScoreVector
ibmCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
NVDNVD · Analyzed3.1Critical9.6CVSS: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
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-77822 badge
[![CVE-2026-77822](https://cveledger.app/badge/CVE-2026-77822.svg)](https://cveledger.app/cve/CVE-2026-77822)

Record last updated .