Skip to main content
Public proof of conceptFix available

CVE-2026-33948

A public proof of concept exists; no exploitation attested.

  • Published2026-04-14
  • Fixed in1.8.2
  • WeaknessCWE-170 · CWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-04-1400:16CVE publishedNVD

Versions per branch

NVD
Jqlang jq
BranchAffectedFixed in
1.8< 1.8.21.8.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • jqlang jq
    Affected
    • = < 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5bno fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-13

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • jqUbuntu:Pro:20.04:LTSall versions · fixed in 1.6-1ubuntu0.20.04.1+esm2
  • jqUbuntu:Pro:18.04:LTSall versions · fixed in 1.5+dfsg-2ubuntu0.1~esm2
  • jqUbuntu:Pro:16.04:LTSall versions · fixed in 1.5+dfsg-1ubuntu0.1+esm4
  • jqUbuntu:Pro:14.04:LTSall versions · fixed in 1.3-1.1ubuntu1.1+esm4
  • jqUbuntu:26.04:LTSall versions · fixed in 1.8.1-4ubuntu2
  • jqUbuntu:25.10all versions · fixed in 1.8.1-3ubuntu1.1
  • jqUbuntu:24.04:LTSall versions · fixed in 1.7.1-3ubuntu0.24.04.2
  • jqUbuntu:22.04:LTSall versions · fixed in 1.6-2.1ubuntu3.2

44 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-33948 Red Hat Product Security5 products fixed · 9 known affected

    jq: jq: Input validation bypass via embedded NUL bytes allows parser differential attacks

    jq.src as a component of Red Hat Enterprise Linux 10 · jq as a component of Red Hat Enterprise Linux 8 · jq-devel as a component of Red Hat Enterprise Linux 8 · +6 more

  • RHSA-2026:8579 Red Hat Product Security5 products fixed

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

Full record on NVD

Fix

  1. Update Jqlang jq to 1.8.2
  2. Vendor fix Red Hat Product Security RHSA-2026:8579 · 5 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
  3. Workaround from the vendor Red Hat Product Security RHSA-2026:8579 · 5 productsMitigation 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.
  4. No fix available, says the vendor Red Hat Product Security CVE-2026-33948 · 9 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2026-04-14
  • CNACVSS 4.02.9known since 2026-10-27
  • NVDCVSS 3.15.3read 2026-10-27
  • CNAweakness (CWE)CWE-170, CWE-20known since 2026-10-27
  • FIRST EPSSEPSS score0.3 %2026-11-18
  • OSVaffected packages—
  • Microsoft MSRCadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CVSS 4.0 vector
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-04-14
Last Modified
2026-10-26
NVD status
Analyzed
MSRC Title
jq: Embedded-NUL Truncation in CLI JSON Input Path Causes Prefix-Only Validation of Malformed Input

Frequently asked questions

What is CVE-2026-33948?

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.

Is CVE-2026-33948 actively exploited?

A proof-of-concept exploit exists for CVE-2026-33948, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-33948?

CVE-2026-33948 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.

Running jq? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record