Evidence · DiggingBeagle record
IBM bulletin: unsafe jq filter expressions in ContextForge
IBM security bulletin on incomplete jq denylist allowing worker process termination or unbounded CPU use in jsonpath_filter.
- Published
- Nov 13, 2026
- Source role
- vendor statement
Evidence record
IBM security bulletin on incomplete jq denylist allowing worker process termination or unbounded CPU use in jsonpath_filter.
Claim-level citations (2)
- supportsA 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. 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.
IBM Security Bulletin CVE-2026-110189, jq filter denylist omissions and fixed 1.1.1 version
- supportsA caller-controlled jq filter could terminate or monopolize a ContextForge worker despite a dangerous-function denylist: 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.
Primary disclosure: results, scope and limitations