CVE-2026-18905 IBM ContextForge MCP Gateway is affected by server-side request forgery via DNS TOCTOU at tool invocation
Remote authenticated attackers can exploit DNS rebinding to perform server-side request forgery and obtain sensitive information.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-18905?
CVE-2026-18905 is a high-severity server-side request forgery vulnerability in IBM ContextForge MCP Gateway (`mcp-contextforge-gateway`), published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-918
Which versions are affected by CVE-2026-18905?
It affects 1 product.
Products include Ibm Contextforge.
How do I fix CVE-2026-18905?
No fix has been published for CVE-2026-18905 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-18905 being exploited?
There is no known exploitation of CVE-2026-18905 in the wild and no public exploit code.
Other vulnerabilities in IBM ContextForge MCP Gateway (`mcp-contextforge-gateway`)
- CVE-2026-78573 IBM ContextForge MCP Gateway is affected by use of default credentials
- CVE-2026-18486 IBM ContextForge MCP Gateway is affected by credential disclosure and privilege escalation via jq filter execution
- CVE-2026-77822 Server-side request forgery in ContextForge MCP Gateway
- CVE-2026-18489 IBM ContextForge Translate is affected by cross-client credential context confusion
- CVE-2026-77825 IBM ContextForge MCP Gateway is affected by path traversal
Sources
Also known as GHSA-p4cr-j9h3-9c8p.