RHSA-2026:8579HighCVSS 8.2

Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

Published
April 16, 2026
Last Modified
September 5, 2026

🔗 CVE IDs covered (6)

CVE-2026-39956 →CVE-2026-39979 →CVE-2026-40164 →CVE-2026-32316 →CVE-2026-33947 →CVE-2026-33948 →

📋 Description

CVE-2026-32316 — jq: jq: Denial of Service or potential arbitrary code execution due to integer overflow and heap-based buffer overflow CVE-2026-33947 — jq: unbounded Recursion in jv_setpath() / jv_getpath() / delpaths_sorted() CVE-2026-33948 — jq: jq: Input validation bypass via embedded NUL bytes allows parser differential attacks CVE-2026-39956 — jq: missing runtime type checks for _strindices lead to crash and limited memory disclosure CVE-2026-39979 — jq: out-of-bounds read in jv_parse_sized() on error formatting for non-NUL-terminated buffers CVE-2026-40164 — jq: jq: Denial of Service via crafted JSON object causing hash collisions

🎯 Affected products4

  • Red Hat Hardened Images
  • jq-main@aarch64 as a component of Red Hat Hardened Images
  • jq-main@src as a component of Red Hat Hardened Images
  • jq-main@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: To mitigate this issue, avoid processing untrusted or unvalidated JSON input with the `jq` utility. Ensure that any scripts or automated processes utilizing `jq` only operate on trusted data sources. Restricting the execution of `jq` to trusted users and environments can also reduce exposure. Workaround: Do not process untrusted input with the jq command line JSON processor. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Do not use untrusted input as an argument to a jq builtin, specifically '_strindices'. Workaround: To mitigate this issue, manually ensure that every buffer is NUL-terminated before passing it to the 'jv_parse_sized' function.

🔗 References (10)