Improper Neutralization of Null Byte or NUL Character Affecting jq package, versions *


Severity

Recommended
medium

Based on Ubuntu security rating.

Threat Intelligence

EPSS
0.16% (5th 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-UBUNTU2004-JQ-16689424
  • published24 Jun 2026
  • disclosed11 May 2026

Introduced: 11 May 2026

CVE-2026-41256  (opens in a new tab)
CWE-158  (opens in a new tab)

How to fix?

There is no fixed version for Ubuntu:20.04 jq.

NVD Description

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

jq is a command-line JSON processor. In 1.8.1 and earlier, Top-level jq programs loaded from a file with -f are truncated at the first embedded NUL byte on current upstream HEAD. A crafted filter file such as . followed by \x00 and arbitrary suffix compiles and executes as only the prefix before the NUL. This leaves jq with a post-CVE-2026-33948 prefix/full-buffer mismatch on the compilation path even though the JSON parser path has already been fixed.

CVSS Base Scores

version 3.1