Quick answers
- Is CVE-2026-54679 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54679 being exploited in the wild.
- How severe is CVE-2026-54679?
- Informational severity, with a CVSS score of 6.9, published 25 June 2026.
- Which products and versions are affected?
- Jqlang Jq < 1.8.2.
- Is there a fix for CVE-2026-54679?
- A patch was published on 2026-06-25: Fix released in version 1.8.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54679 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-54679?
- Check whether you run Jqlang Jq at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow vulnerability exists in the `jvp_string_append` function in `src/jv.c` of jq when running on 32-bit architectures. The software attempts to prevent overflows by checking if the combined length of strings exceeds `INT_MAX`, but subsequently doubles the allocation size using 32-bit arithmetic. On 32-bit systems, the calculation `(currlen + len) * 2` can result in a value that, when passed to `jvp_string_alloc`, causes `sizeof(jvp_string) + size + 1` to wrap around `size_t`. This leads to a very small memory allocation followed by a large `memcpy` operation, resulting in a heap-based buffer overflow. An attacker providing malicious JSON input could trigger this overflow to cause a denial of service or potentially execute arbitrary code. The issue is resolved in version 1.8.2.
Affected products
- jqlang jq < 1.8.2
Timeline
- 2026-06-16: advisory: GitHub Security Advisory published
- 2026-06-25: disclosed: CVE published to NVD
- 2026-06-25: patched: Fix released in version 1.8.2