Out-of-bounds Read Affecting jq-debuginfo package, versions <0:1.8.1-59.amzn2023


Severity

Recommended
medium

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.56% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-JQDEBUGINFO-17290342
  • published10 Jun 2026
  • disclosed13 Apr 2026

Introduced: 13 Apr 2026

CVE-2026-39979  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 jq-debuginfo to version 0:1.8.1-59.amzn2023 or higher.
This issue was patched in ALAS2023-2026-1815.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jq-debuginfo package and not the jq-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.

CVSS Base Scores

version 3.1