cve.bz

CVE-2026-33948 jqlang jq: Improper Null Termination

2.9 lowExploit referenceEPSS 0.3%Fix available

Low (2.9) in jqlang jq. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
jq is a command-line JSON processor. Commits before 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b contain a vulnerability where CLI input parsing allows validation bypass via embedded NUL bytes. When reading JSON from files or stdin, jq uses strlen() to determine buffer length instead of the actual byte count from fgets(), causing it to truncate input at the first NUL byte and parse only the preceding prefix. This enables an attacker to craft input with a benign JSON prefix before a NUL byte followed by malicious trailing data, where jq validates only the prefix as valid JSON while silently discarding the suffix. Workflows relying on jq to validate untrusted JSON before forwarding it to downstream consumers are susceptible to parser differential attacks, as those consumers may process the full input including the malicious trailing bytes. This issue has been patched by commit 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b.

Severity

CVSS 4.0

2.9 low
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 19th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-04-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-170 Improper Null Termination
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-33948 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33948?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33948?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33948 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-33948

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-33948](https://cve.bz/cve/badge/CVE-2026-33948.svg)](https://cve.bz/cve/CVE-2026-33948)

HTML:

<a href="https://cve.bz/cve/CVE-2026-33948"><img src="https://cve.bz/cve/badge/CVE-2026-33948.svg" alt="CVE-2026-33948"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jqlang:jqbefore 1.8.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12jq1.6-2.1+deb12u2DEBIAN-CVE-2026-33948
Debian13jq1.7.1-6+deb13u2DEBIAN-CVE-2026-33948
Debian14jq1.8.1-5DEBIAN-CVE-2026-33948
Ubuntu22.04:LTSjq1.6-2.1ubuntu3.2UBUNTU-CVE-2026-33948 USN-8202-1
Ubuntu24.04:LTSjq1.7.1-3ubuntu0.24.04.2UBUNTU-CVE-2026-33948 USN-8202-1
Ubuntu25.10jq1.8.1-3ubuntu1.1UBUNTU-CVE-2026-33948 USN-8202-1
Ubuntu26.04:LTSjq1.8.1-4ubuntu2UBUNTU-CVE-2026-33948
UbuntuPro:14.04:LTSjq1.3-1.1ubuntu1.1+esm4USN-8202-1
UbuntuPro:16.04:LTSjq1.5+dfsg-1ubuntu0.1+esm4UBUNTU-CVE-2026-33948 USN-8202-1
UbuntuPro:18.04:LTSjq1.5+dfsg-2ubuntu0.1~esm2UBUNTU-CVE-2026-33948 USN-8202-1
UbuntuPro:20.04:LTSjq1.6-1ubuntu0.20.04.1+esm2UBUNTU-CVE-2026-33948 USN-8202-1
Red Hathummingbird:1jq, jq-devel0:1.8.1-3.hum1RHSA-2026:8579
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 11 morejq1.7.1-150000.3.25.1SUSE-SU-2026:4275-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0jq1.7.1-160000.3.1SUSE-SU-2026:22566-1
SUSELinux Micro 6.0jq1.6-6.1SUSE-SU-2026:22705-1
SUSELinux Micro 6.0jq1.7.1-1.1SUSE-SU-2026:23873-1
SUSELinux Micro 6.1jq1.7.1-slfo.1.1_3.1SUSE-SU-2026:22664-1
SUSELinux Micro 6.2jq1.7.1-160000.3.1SUSE-SU-2026:22545-1
openSUSELeap 16.0jq1.7.1-160000.3.1openSUSE-SU-2026:21248-1
openSUSETumbleweedjq1.8.1-3.1openSUSE-SU-2026:10850-1
Alpinev3.21, v3.22, v3.23 and 1 morejq1.8.2-r0ALPINE-CVE-2026-33948
Azure Linux3jq1.7.1-5AZL-82928
Alpaquita23, streamjq1.8.1-r1BELL-CVE-2026-33948
Alpaquita25jq1.8.1-r2BELL-CVE-2026-33948

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's 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.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat Hardened Imagesjq-main-1.8.1-3.hum1Fixed 2026-04-16RHSA-2026:8579
Red Hat Enterprise Linux 10jqFix deferred
Red Hat Enterprise Linux 8jqFix deferred
Red Hat Enterprise Linux 9jqFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-33948.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON