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…
Inspect the ClaimsCase · DiggingBeagle record
OAuth 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.
Public disclosure: Nov 13, 2026
An authenticated user can configure or cause gateway interaction with an OAuth authorization server whose metadata advertises a registration endpoint.
At a glance
The advertised endpoint is treated as a trusted network destination for gateway-origin HTTP without independent address validation.
Read the implicationsThe vulnerability is in OAuth discovery and DCR metadata, distinct from the unrelated ContextForge jq/schema denial-of-service defects and token-cache identity bug.
Limits and uncertaintyFull account
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 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.
Mechanism and trust boundary
- 01
Starting condition
An authenticated user can configure or cause gateway interaction with an OAuth authorization server whose metadata advertises a registration endpoint.
Boundary: precondition and attacker capability
- 02
Trust boundary crossed or evaluated
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.
Boundary: mechanism
- 03
Observed consequence
The advertised endpoint is treated as a trusted network destination for gateway-origin HTTP without independent address validation.
Boundary: observed effect and limitations
Claims & evidence
CLM-NOV15-CF110194-MECHContextForge 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.supported
Basis: reported finding
- supportsIBM bulletin: ContextForge OAuth dynamic registration SSRFvendor statement
IBM Security Bulletin CVE-2026-110194, OAuth metadata RFC 7591 DCR and version/workaround details
CLM-NOV15-CF110194-SCOPEIBM 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.supported
Basis: reported finding
- supportsIBM bulletin: ContextForge OAuth dynamic registration SSRFvendor statement
Primary disclosure: results, scope and limitations
Implications
The advertised endpoint is treated as a trusted network destination for gateway-origin HTTP without independent address validation.
Controls and mitigations
- Install the fixed 1.1.0 or later DCR destination checks, and independently confine the gateway egress network.
- Where updating is not possible, restrict DCR_ALLOWED_ISSUERS or disable dynamic registration without accidentally disabling unrelated OAuth authorization requirements.
Unknowns and contradictions
- 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.
Sources and citation
Material revision history
- Nov 15, 2026 · Canonical change recorded · new in release · revision 250