LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

jq can misread a filter file if it contains an embedded NUL byte, running only the part before that byte. This can change intended data-processing logic when a user or workflow loads jq programs from files. The issue is local and requires someone to use a malicious or tampered filter file.

Executive priority

Treat as moderate priority. It is not remotely exploitable based on the provided evidence, but it can affect integrity in automation that trusts jq filter files. Prioritize environments where jq filters are supplied through repositories, artifacts, or shared workspaces.

Technical view

CVE-2026-41256 affects jqlang jq 1.8.1 and earlier. Top-level jq programs loaded with -f are truncated at the first embedded NUL byte, creating a prefix/full-buffer mismatch in the compilation path. CVSS 3.1 is 5.5, with local access, low complexity, user interaction, and high integrity impact.

Likely exposure

Exposure is most likely in scripts, CI jobs, build pipelines, or data-processing automation that invoke jq with -f and accept filter files from untrusted or weakly controlled sources.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Exploitation requires local use of a crafted or modified jq filter file, so risk depends heavily on who can influence files passed to jq with -f.

Researcher notes

Focus analysis on the -f compilation path and embedded NUL handling. The provided description ties this to a post-CVE-2026-33948 prefix/full-buffer mismatch while noting the JSON parser path was already fixed. No exploit-in-the-wild evidence is provided.

Mitigation direction

  • Review the GitHub advisory for vendor-confirmed fixes or workarounds.
  • Update jq when a vendor-confirmed fixed release is identified.
  • Restrict jq filter files to trusted, reviewable sources.
  • Reject or quarantine filter files containing embedded NUL bytes.
  • Protect CI and automation workspaces from untrusted file modification.

Validation and detection

  • Inventory systems running jq 1.8.1 or earlier.
  • Search automation for jq invocations using -f.
  • Identify workflows where filter files come from users, repositories, artifacts, or temporary directories.
  • Check whether controls detect embedded NUL bytes in jq filter files.
  • Confirm vendor guidance before declaring remediation complete.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-158: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41256 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N1.83.6GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2026-41256Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
jqlangjq<= 1.8.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-158 · source CWE mapping

Improper Neutralization of Null Byte or NUL Character

Improper Neutralization of Null Byte or NUL Character represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.