CVE-2026-43895

medium

Published 2026-05-11 · Modified 2026-05-13

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

4.4

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CVSS v4 NEW

—

not yet in upstream

VIR risk

4.4

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.

Predictions

Exploit likelihood

44%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OS	Version	Status	Fixed in
debian	bookworm	affected
debian	bullseye	fixed	`1.6-2.1+deb11u2`
debian	forky	fixed	`1.8.1-6`
debian	sid	fixed	`1.8.1-6`
debian	trixie	affected
sles		affected
windows		affected

Application impact

Vendor	Product	Versions	Fixed
jqlang	jq	`{"endIncluding":"1.8.1"}`

References

CWEs

CWE-20 CWE-158

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.