The ContextForge tool-response transformation path exposed a jsonpath_filter accepted from an authenticated remote caller. The code attempted to reject dangerous jq built-ins using an incomplete blacklist rather than enforcing a bounded expression language or process resource limit. IBM identifies halt, halt_error and unbounded-iteration classes as…
Inspect the ClaimsCase · DiggingBeagle record
A caller-controlled jq filter could terminate or monopolize a ContextForge worker despite a dangerous-function denylist
The ContextForge tool-response transformation path exposed a jsonpath_filter accepted from an authenticated remote caller. The code attempted to reject dangerous jq built-ins using an incomplete blacklist rather than enforcing a bounded expression language or process resource limit.
Public disclosure: Nov 13, 2026
An authenticated caller can supply response filters through a gateway feature enabled in the deployment.
At a glance
A syntactically accepted filter can exceed the worker execution budget or terminate its evaluator process, disrupting unrelated agent calls.
Read the implicationsThe MCP-specific risk is that tool data transformation inherits availability authority over a common gateway process.
Limits and uncertaintyFull account
The ContextForge tool-response transformation path exposed a jsonpath_filter accepted from an authenticated remote caller. The code attempted to reject dangerous jq built-ins using an incomplete blacklist rather than enforcing a bounded expression language or process resource limit.
IBM identifies halt, halt_error and unbounded-iteration classes as omissions that can reach the jq evaluator and terminate a worker or force prolonged execution. This is not the same path as catastrophic regular expressions in registered JSON Schemas.
CVE-2026-110189 affects 1.0.8 through 1.0.11 and 1.1.0, with IBM directing users to 1.1.1. The bulletin does not establish an actual production outage or arbitrary operating-system execution.
The MCP-specific risk is that tool data transformation inherits availability authority over a common gateway process.
Mechanism and trust boundary
- 01
Starting condition
An authenticated caller can supply response filters through a gateway feature enabled in the deployment.
Boundary: precondition and attacker capability
- 02
Trust boundary crossed or evaluated
IBM identifies halt, halt_error and unbounded-iteration classes as omissions that can reach the jq evaluator and terminate a worker or force prolonged execution. This is not the same path as catastrophic regular expressions in registered JSON Schemas.
Boundary: mechanism
- 03
Observed consequence
A syntactically accepted filter can exceed the worker execution budget or terminate its evaluator process, disrupting unrelated agent calls.
Boundary: observed effect and limitations
Claims & evidence
CLM-NOV15-CF110189-MECHThe ContextForge tool-response transformation path exposed a jsonpath_filter accepted from an authenticated remote caller. The code attempted to reject dangerous jq built-ins using an incomplete blacklist rather than enforcing a bounded expression language or process resource limit. IBM identifies halt, halt_error and unbounded-iteration classes as omissions that can reach the jq evaluator and terminate a worker or force prolonged execution. This is not the same path as catastrophic regular expressions in registered JSON Schemas.supported
Basis: reported finding
- supportsIBM bulletin: unsafe jq filter expressions in ContextForgevendor statement
IBM Security Bulletin CVE-2026-110189, jq filter denylist omissions and fixed 1.1.1 version
CLM-NOV15-CF110189-SCOPECVE-2026-110189 affects 1.0.8 through 1.0.11 and 1.1.0, with IBM directing users to 1.1.1. The bulletin does not establish an actual production outage or arbitrary operating-system execution. The MCP-specific risk is that tool data transformation inherits availability authority over a common gateway process.supported
Basis: reported finding
- supportsIBM bulletin: unsafe jq filter expressions in ContextForgevendor statement
Primary disclosure: results, scope and limitations
Implications
A syntactically accepted filter can exceed the worker execution budget or terminate its evaluator process, disrupting unrelated agent calls.
Controls and mitigations
- Upgrade to ContextForge 1.1.1 or later and sandbox filter execution with strict time/CPU/process containment.
- Treat filter allowlisting as a structural expression-language problem, not a list of suspicious words alone.
Unknowns and contradictions
- The MCP-specific risk is that tool data transformation inherits availability authority over a common gateway process.
Sources and citation
Material revision history
- Nov 15, 2026 · Canonical change recorded · new in release · revision 250