You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
jq vulnerability
About this tag
The jq vulnerability tag covers a series of moderate-severity CVEs published in 2026, including CVE-2026-41257 (integer overflow), CVE-2026-41256 (NUL byte truncation), CVE-2026-43895 (import path NUL bug), and CVE-2026-43896 (recursive merge DoS). These flaws affect jq, a command-line JSON processor widely used in scripts, CI/CD pipelines, containers, and cross-platform automation. While not Windows desktop vulnerabilities, they are listed in Microsoft's Security Update Guide because jq is part of the toolchain in Azure Linux, WSL, and other environments that Windows administrators manage. The recurring themes are supply chain risk, trust in open-source utilities, and the operational impact of small parsing bugs in critical glue code.
CVE-2026-41257 is a newly published jq vulnerability, released in Microsoft’s Security Update Guide on May 13, 2026 and updated on June 3, affecting Azure Linux 3.0 jq packages where a signed integer overflow in the jq virtual machine stack can corrupt memory. The bug is not a Windows desktop...
Microsoft’s Security Update Guide now lists CVE-2026-41256, a moderate-severity jq vulnerability published in May 2026 in which top-level jq filter programs loaded with -f can be silently truncated at an embedded NUL byte. The bug is not a Windows kernel emergency or a remote wormable flaw, but...
CVE-2026-43895 is a moderate-severity jq vulnerability, published in May 2026 and tracked by GitHub, NVD, and Microsoft’s Security Update Guide, in which embedded NUL characters in jq import paths can make local automation validate one file name while jq opens another. That sounds narrow, and in...
Microsoft’s Security Update Guide lists CVE-2026-43896 as a jq denial-of-service vulnerability disclosed in May 2026, affecting jq 1.8.1 and earlier when recursive object merges can trigger unbounded recursion and crash the process. That sounds narrow until you remember where jq lives: in shell...