jq: Embedded-NUL Truncation in CLI JSON Input Path Causes Prefix-Only Validation of Malformed Input
jqlang · jq
Official source article: GitHub GHSA-32CX-CVVH-2WJ9 ↗. Check the applicable product and release in the original source.
2.9LowCVSS 4.0
Recommended action
Within 7 days
Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Published severityLow→Operational priority:Medium, raised one band.upgradedsince 14 Apr 2026
Evidence used
No CISA KEV confirmation is currently recorded.
A structured source references public exploit or proof-of-concept material.
The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
EPSS is 0.35% for the current model date.
Compensating controls
Validate the affected product branch and deploy the verified fixed release.
Restrict the affected network interface to trusted sources where business-safe.
Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
Confirm that the asset runs jqlang jq and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
Release-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
7 package states
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Distribution release
Source package
Vendor state
Fixed version
Evidence
Alpine v3.23v3.23 · main
jq
Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.
Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
jq as a component of Red Hat Enterprise Linux 10
jq-devel as a component of Red Hat Enterprise Linux 10
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
jq.src as a component of Red Hat Enterprise Linux 8
jq as a component of Red Hat Enterprise Linux 9
jq-devel as a component of Red Hat Enterprise Linux 9
jq.src as a component of Red Hat Enterprise Linux 9
openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
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.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
1 current
ENISA EUVD identifier
EUVD-2026-22158
No EUVD known-exploited evidence
ENISA has published the identifier mapping but no EUVD description has been stored yet.
EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
Low technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
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.
What
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.
Why
The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
Likely attack path
a network path → Improper Null Termination → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-170: Improper Null Termination. The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VILowVulnerable-system integrity: A successful attack can cause a limited loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-22158Official EUVD mapping
0 linked advisory records.
Official EUVD record ↗Cyber Security Agency of Singapore · English · CSA-SB-20260415Security Bulletin 15 April 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 April 2026, published on 15 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
Official advisory ↗CERT-FR · French · CERTFR-2026-AVI-0463Multiples vulnérabilités dans les produits Microsoft
sécurité Microsoft CVE-2026-31421 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-31422 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-31423 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-31424 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-31426 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-31427 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-31428 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-40393 du 14 avril 2026
Bulletin de sécurité Microsoft CVE-2026-32316 du 17 avril 2026
Bulletin de sécurité Microsoft CVE-2026-33947 du 17 avril 2026
Bulletin de sécurité Microsoft CVE-2026-33948 du 17 avril 2026
Bulletin de sécurité Microsoft CVE-2026-39956 du 17 avril 2026
Bulletin de sécurité Microsoft CVE-2026-39979 du 17 avril 2026
Bulletin de sécurité Microsoft CVE-2026-40164 du 17 avril 2026
Bulletin de sécurité Microsoft CVE-2025-70873 du 18 avril 2026
Une gestion de version détaillée se trouve à la fin de ce document.
Risque
Non spécifié par l'éditeur
Systèmes affectés
azl3 cups 2.4.16-1 versions antérieures à 2.4.17-1
azl3 jq 1.7.1-4 versions antérieures à 1.7.1-5
azl3 kernel 6.6.130.1-3 versions antérieures à 6.6.134.1-1
azl3 mesa 24.0.1-6 versions antérieures à 24.0.1-8
azl3 pytorch 2.2.2-12 versions antérieures à 2.2.2-1
Official advisory ↗JVN iPedia · Japanese · JVNDB-2026-012113jqlangのjqにおける複数の脆弱性
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 13 Apr 2026 · Last source change 14 Apr 2026, 15:53 UTC · CWE-170 · Improper Null Termination
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-22158
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
< 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
After
< 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Affected versionsThe structured affected or fixed version information changed.
Before
jq as a component of Red Hat Enterprise Linux 10; jq-devel as a component of Red Hat Enterprise Linux 10; 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; jq.src as a component of Red Hat Enterprise Linux 8; jq as a component of Red Hat Enterprise Linux 9; jq-devel as a component of Red Hat Enterprise Linux 9; jq.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: jq-main@aarch64 as a component of Red Hat Hardened Images; jq-main@src as a component of Red Hat Hardened Images; jq-main@x86_64 as a component of Red Hat Hardened Images
After
jq as a component of Red Hat Enterprise Linux 10; jq-devel as a component of Red Hat Enterprise Linux 10; 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; jq.src as a component of Red Hat Enterprise Linux 8; jq as a component of Red Hat Enterprise Linux 9; jq-devel as a component of Red Hat Enterprise Linux 9; jq.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: jq-main@aarch64 as a component of Red Hat Hardened Images; jq-main@src as a component of Red Hat Hardened Images; jq-main@x86_64 as a component of Red Hat Hardened Images
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.