Vulnerability in jq
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as ALPINE-CVE-2026-33947 has been found in jq.
Risk of unauthorized operations or information disclosure.
What to do: upgrade jq to 1.8.2-r0 or later.
If unsure, ask your IT team or search "jq ALPINE-CVE-2026-33947" on the vendor's site.
ALPINE-CVE-2026-33947 (jq)
Attack vector: local / no user interaction
Patched: 1.8.2-r0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in jq.
Check the vendor advisory for the affected versions of jq.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.8.2-r0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'jq' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'jq' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jqを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade jq to 1.8.2-r0ステージング環境で 1.8.2-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Alpine:v3.22 | jq |
< 1.8.2-r0 |
1.8.2-r0 |
| Alpine:v3.23 | jq |
< 1.8.2-r0 |
1.8.2-r0 |
| Alpine:v3.24 | jq |
< 1.8.2-r0 |
1.8.2-r0 |
Original description The description as published by the source.
jq is a command-line JSON processor. In versions 1.8.1 and below, functions jv_setpath(), jv_getpath(), and delpaths_sorted() in jq's src/jv_aux.c use unbounded recursion whose depth is controlled by the length of a caller-supplied path array, with no depth limit enforced. An attacker can supply a JSON document containing a flat array of ~65,000 integers (~200 KB) that, when used as a path argument by a trusted jq filter, exhausts the C call stack and crashes the process with a segmentation fault (SIGSEGV). This bypass works because the existing MAX_PARSING_DEPTH (10,000) limit only protects the JSON parser, not runtime path operations where arrays can be programmatically constructed to arbitrary lengths. The impact is denial of service (unrecoverable crash) affecting any application or service that processes untrusted JSON input through jq's setpath, getpath, or delpaths builtins. This issue has been addressed in commit fb59f1491058d58bdc3e8dd28f1773d1ac690a1f.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security.alpinelinux.org