# CVE-2026-41256: jq: Embedded NUL truncates top-level jq programs loaded with -f

> Attackers can execute arbitrary jq code by crafting a filter file with embedded NUL bytes, bypassing intended program restrictions.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 May 2026
- **Updated:** 23 Jun 2026
- **Also known as:** ALPINE-CVE-2026-41256, AZL-86384, BELL-CVE-2026-41256, DEBIAN-CVE-2026-41256, ECHO-0fbb-9ca8-7649, GHSA-vf2h-chrj-q3fg, UBUNTU-CVE-2026-41256

## What is CVE-2026-41256?

CVE-2026-41256 is a medium-severity code injection vulnerability in jqlang jq, published on 11 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

jq is a command-line JSON processor. In 1.8.1 and earlier, Top-level jq programs loaded from a file with -f are truncated at the first embedded NUL byte on current upstream HEAD. A crafted filter file such as . followed by \x00 and arbitrary suffix compiles and executes as only the prefix before the NUL. This leaves jq with a post-CVE-2026-33948 prefix/full-buffer mismatch on the compilation path even though the JSON parser path has already been fixed.

Weakness: CWE-158 (Improper Neutralization of Null Byte or NUL Character)

## Which versions are affected by CVE-2026-41256?

It affects 1 product.


Products: Jqlang Jq.

## How do I fix CVE-2026-41256?

Apply the vendor's patch.

## Is CVE-2026-41256 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41256 exists.

## Other vulnerabilities in jqlang jq

- [CVE-2026-32316](https://insights.sbomify.com/CVE-2026-32316/): jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow (high 8.2)
- [CVE-2024-53427](https://insights.sbomify.com/CVE-2024-53427/): Memory corruption in jq (high 8.1)
- [CVE-2025-48060](https://insights.sbomify.com/CVE-2025-48060/): AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt) (high 7.7)
- [CVE-2023-49355](https://insights.sbomify.com/CVE-2023-49355/): Memory corruption in n/a (high 7.5)
- [CVE-2026-49839](https://insights.sbomify.com/CVE-2026-49839/): jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41256 and fix it if it is affected.

What it is: CVE-2026-41256 is a medium-severity code injection vulnerability in jqlang jq, published on 11 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41256 exists.

Affected product: jqlang jq. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41256/ (Markdown: https://insights.sbomify.com/CVE-2026-41256/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41256
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41256
- OSV: https://osv.dev/vulnerability/CVE-2026-41256

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41256/
Summaries are generated and may contain mistakes; the official description above is the record.