CVE-2026-43895: jq: Embedded NUL in jq import paths causes local redaction-policy bypass and preserves sensitive fields in published artifacts
jq is a command-line JSON processor. In 1.8.1 and earlier, jq accepts embedded NUL bytes in import paths at the jq-language level, but later resolves those paths through C string operations during module and data-file lookup. This creates a mismatch between the logical import string that policy or audit code may validate and the on-disk path that jq actually opens.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43895?
CVE-2026-43895 is classified as a high-severity vulnerability due to its potential to bypass local redaction policies.
How do I fix CVE-2026-43895?
To mitigate CVE-2026-43895, users should upgrade jq to version 1.8.2 or later, which resolves the issue with embedded NUL bytes.
What software is affected by CVE-2026-43895?
CVE-2026-43895 affects jq versions 1.8.1 and earlier, including those from the Stedolan jq project.
What is the main risk associated with CVE-2026-43895?
The main risk of CVE-2026-43895 is the potential exposure of sensitive fields in published artifacts due to the bypass of local redaction policies.
Is there a workaround for CVE-2026-43895 if I cannot upgrade jq?
Currently, the recommended action for CVE-2026-43895 is to upgrade jq; no specific workarounds are provided to resolve the vulnerability.