Vulnerability in jq (CVE-2026-47770)
Summary
Vulnerability in jq (CVE-2026-47770). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.2 or later.
Original description
The description as published by the source.
jq is a command-line JSON processor. Prior to 1.8.2, comparing two sufficiently deeply nested arrays with the == operator exhausts the C stack on jq's ordinary command-line surface, resulting in denial of service via stack exhaustion (uncontrolled recursion). The crash occurs in jq's recursive structural comparison code, with the recursion repeating through jvp_array_equal() and jv_equal() in src/jv.c when comparing deeply nested arrays; a nearby sort comparator path through jv_cmp() in src/jv_aux.c overflows the stack at a larger nesting depth from the same missing recursion guard. Anyone running jq comparisons on attacker-controlled deeply nested JSON values, or embedding jq in a context where untrusted data can reach the == comparison path, is affected. This vulnerability is fixed in 1.8.2.
Source: NIST National Vulnerability Database NVD
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 CVE-2026-47770 has been found in jq.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade jq to 1.8.2 or later.
If unsure, ask your IT team or search "jq CVE-2026-47770" on the vendor's site.
CVE-2026-47770 (jq) — CWE-674 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 1.8.2 — 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 (CWE-674) exists in jq.
Check the vendor advisory for the affected versions of jq.
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.8.2.
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
-
1Identify exposure identify
grep -r 'jq' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
jqを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade jq to 1.8.2ステージング環境で 1.8.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-47770 jq Fixed in: 1.8.1-r1
- Debian DEBIAN-CVE-2026-47770 jq
- Ubuntu UBUNTU-CVE-2026-47770 jq
References
- exploit security-advisories@github.com