PatchSiren cyber security CVE debrief
CVE-2026-33948 Jqlang CVE debrief
CVE-2026-33948 is a low-severity vulnerability in the jq command-line JSON processor. The vulnerability allows validation bypass via embedded NUL bytes when reading JSON from files or stdin. An attacker can craft input with a benign JSON prefix before a NUL byte followed by malicious trailing data, which jq validates only the prefix as valid JSON while silently discarding the suffix. This issue has been patched by commit 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b.
- Vendor
- Jqlang
- Product
- Jq
- CVSS
- LOW 2.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-14
- Original CVE updated
- 2026-10-26
- Advisory published
- 2026-04-14
- Advisory updated
- 2026-10-26
Who should care
Defenders who manage jq installations, especially in workflows that rely on jq to validate untrusted JSON before forwarding it to downstream consumers, should assess exposure and prioritize verifying the patch status of jq installations.
Why it matters
CVE-2026-33948 is a low-severity vulnerability in jq that allows validation bypass via embedded NUL bytes. Defenders should prioritize verifying the patch status of jq installations, especially in workflows that rely on jq to validate untrusted JSON.
- Parser differential attacks may occur if untrusted JSON is not properly validated
- Verification of patch status is required to prevent exploitation
- Compensating controls may be necessary to mitigate parser differential attacks
Technical summary
The vulnerability in jq allows validation bypass via embedded NUL bytes when reading JSON from files or stdin. An attacker can craft input with a benign JSON prefix before a NUL byte followed by malicious trailing data, which jq validates only the prefix as valid JSON while silently discarding the suffix. This issue enables parser differential attacks if untrusted JSON is not properly validated, and defenders should prioritize verifying the patch status of jq installations, especially in workflows that rely on jq to validate untrusted JSON before forwarding it to downstream consumers.
Defensive priority
Defenders should prioritize verifying the patch status of jq installations, especially in workflows that rely on jq to validate untrusted JSON before forwarding it to downstream consumers.
Recommended defensive actions
- Verify the patch status of jq installations
- Assess exposure in workflows that rely on jq to validate untrusted JSON
- Implement compensating controls to mitigate parser differential attacks
- Review jq installation configurations for potential vulnerabilities
- Monitor jq logs for suspicious activity
- Perform regular security audits of jq installations
- Update jq to the latest version
Evidence notes
The CVE record and NVD vulnerability detail provide information on the vulnerability, its impact, and the patch status. However, the corpus does not establish versions, exploitation, impact, or remediation for all affected systems, requiring verification from the supplied official sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-33948 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-33948
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-33948 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-33948
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/jqlang/jq/commit/6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/jqlang/jq/security/advisories/GHSA-32cx-cvvh-2wj9
[email protected] - Exploit, Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.