CVE-2026-18905 json
IBM ContextForge MCP Gateway is affected by server-side request forgery via DNS TOCTOU at tool invocation
published 2mo ago modified last mo. also EUVD-2026-71315
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
IBM ContextForge MCP Gateway (`mcp-contextforge-gateway`) <= v1.0.6 MCP Context Forge could allow a remote authenticated attacker to obtain sensitive information due to a DNS rebinding vulnerability during tool invocation.
Patch / fix
- ibm.com/support/pages/node/7286053 advisory
Is CVE-2026-18905 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Affected products
- IBM ContextForge MCP Gateway (`mcp-contextforge-gateway`)
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
ibm.com
/support/pages/node/7286053
vendor-advisory, patch
Sources
- CVE List CVE-2026-18905
- NVD CVE-2026-18905
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.