CVE-2026-43895: CWE-20: Improper Input Validation in jqlang jq
jq versions 1.8.1 and earlier contain an improper input validation vulnerability related to embedded NUL bytes in import paths. The jq language parser accepts these NUL bytes, but the underlying file path resolution uses C string operations that terminate at the NUL byte, causing a mismatch between the validated import string and the actual file accessed. This discrepancy can lead to unintended file access. The vulnerability has a medium severity with a CVSS score of 4.4. No official patch or remediation has been confirmed at this time.
AI Analysis
Technical Summary
CVE-2026-43895 describes an improper input validation vulnerability in jq (versions <=1.8.1) where embedded NUL bytes in import paths are accepted by the jq language parser but truncated during file path resolution due to C string handling. This mismatch allows an attacker to cause jq to access files different from those intended by the validated import string, potentially leading to unintended file access. The vulnerability is rated medium severity with a CVSS 3.1 score of 4.4. There is no confirmed official patch or remediation available as of the published date.
Potential Impact
The vulnerability can result in unintended file access due to the mismatch between the import path validation and actual file path resolution. This may allow an attacker with local privileges to cause jq to read files other than those intended, potentially exposing sensitive information. The impact is limited to confidentiality and integrity with no availability impact. Exploits in the wild are not known.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should exercise caution when processing untrusted import paths with jq versions 1.8.1 and earlier. Consider restricting jq usage to trusted inputs or environments.
CVE-2026-43895: CWE-20: Improper Input Validation in jqlang jq
Description
jq versions 1.8.1 and earlier contain an improper input validation vulnerability related to embedded NUL bytes in import paths. The jq language parser accepts these NUL bytes, but the underlying file path resolution uses C string operations that terminate at the NUL byte, causing a mismatch between the validated import string and the actual file accessed. This discrepancy can lead to unintended file access. The vulnerability has a medium severity with a CVSS score of 4.4. No official patch or remediation has been confirmed at this time.
CVSS v3.1
Score 4.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-43895 describes an improper input validation vulnerability in jq (versions <=1.8.1) where embedded NUL bytes in import paths are accepted by the jq language parser but truncated during file path resolution due to C string handling. This mismatch allows an attacker to cause jq to access files different from those intended by the validated import string, potentially leading to unintended file access. The vulnerability is rated medium severity with a CVSS 3.1 score of 4.4. There is no confirmed official patch or remediation available as of the published date.
Potential Impact
The vulnerability can result in unintended file access due to the mismatch between the import path validation and actual file path resolution. This may allow an attacker with local privileges to cause jq to read files other than those intended, potentially exposing sensitive information. The impact is limited to confidentiality and integrity with no availability impact. Exploits in the wild are not known.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should exercise caution when processing untrusted import paths with jq versions 1.8.1 and earlier. Consider restricting jq usage to trusted inputs or environments.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-04T15:17:09.330Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a021aa7cbff5d861043052e
Added to database: 05/11/2026, 18:06:31 UTC
Last enriched: 07/02/2026, 23:38:45 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 74
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.