CVE-2026-33948
jq: jq: Input validation bypass via embedded NUL bytes allows parser differential attacks
Severity
LowRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · April 14, 2026
Updated · September 1, 2026
Description
A flaw was found in jq, a command-line JSON processor. This vulnerability allows a remote attacker to bypass input validation by crafting malicious JSON input containing embedded null (NUL) bytes. Due to incorrect handling of input buffer lengths, jq truncates the input at the first NUL byte, validating only the benign prefix and silently discarding any malicious data that follows. This can lead to parser differential attacks where downstream systems, relying on jq for validation, may process the full, unvalidated input, potentially leading to unexpected behavior or security compromises.
Statement
This vulnerability in jq allows an attacker to bypass input validation by embedding NUL bytes in JSON input. This is relevant in Red Hat environments where jq is used to validate untrusted JSON before it is processed by other tools, potentially leading to parser differential attacks and unexpected behavior in downstream systems. The jq command line tool is not exposed to the network in default configurations of Red Hat products.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
Mitigation
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.
CVSS / CWE
CVSS 3.1 · 3.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
CWE-170 · Improper Null Termination