Evidence · DiggingBeagle record
IBM bulletin: ContextForge OAuth dynamic registration SSRF
IBM bulletin: authorization-server metadata supplied dynamic client registration endpoints without destination validation.
- Published
- Nov 13, 2026
- Source role
- vendor statement
Evidence record
IBM bulletin: authorization-server metadata supplied dynamic client registration endpoints without destination validation.
Claim-level citations (2)
- supportsOAuth server metadata could redirect ContextForge registration traffic toward internal network destinations: ContextForge supports OAuth Dynamic Client Registration and reads an authorization server metadata document to learn where to send registration, update or delete requests. The vulnerable gateway trusted that metadata endpoint without sufficient URL or destination validation. An authenticated actor able to influence authorization-server metadata could cause the gateway to issue HTTP requests from its privileged network toward internal addresses. The actual response and data exposure depend on reachable resources, network policy and allowed methods.
IBM Security Bulletin CVE-2026-110194, OAuth metadata RFC 7591 DCR and version/workaround details
- supportsOAuth server metadata could redirect ContextForge registration traffic toward internal network destinations: IBM identifies CVE-2026-110194, versions 1.0.0 through 1.0.11, fixed in 1.1.0. The bulletin does not establish cloud metadata theft, compromise or a verified external attack. Disabling DCR or restricting trusted issuers is a conditional workaround. The vulnerability is in OAuth discovery and DCR metadata, distinct from the unrelated ContextForge jq/schema denial-of-service defects and token-cache identity bug.
Primary disclosure: results, scope and limitations