BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-43895High confidence

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

jqlang · jq

Official source article: GitHub GHSA-7Q7G-MRQ3-PHXR ↗. Check the applicable product and release in the original source.

4.4MediumCVSS 3.1
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs jqlang jq and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainjqVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.8.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainjqVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.8.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.7.1-6+deb13u3Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.6-2.1+deb12u2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.8.1-6Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.8.1-6Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivejqUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-43895 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-43895
51 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • jq as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • libjq-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • libjq1 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • jq as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • libjq-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • libjq1 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • jq as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • libjq-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • libjq1 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • jq as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • libjq-devel as component of SUSE Linux Enterprise Server 15 SP1-LTSS
  • libjq1 as component of SUSE Linux Enterprise Server 15 SP1-LTSS
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-43895 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjq: embedded NUL in jq import paths causes local redaction-policy bypass and preserves sensitive fields in published artifacts
15 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • automation-controller.src as a component of Red Hat Ansible Automation Platform 2
  • jq.src as a component of Red Hat Ceph Storage 4
  • jq as a component of Red Hat Enterprise Linux 10
  • jq-devel as a component of Red Hat Enterprise Linux 10
  • jq.src as a component of Red Hat Enterprise Linux 10
  • jq as a component of Red Hat Enterprise Linux 8
  • jq-devel as a component of Red Hat Enterprise Linux 8
  • jq.src as a component of Red Hat Enterprise Linux 8
  • jq as a component of Red Hat Enterprise Linux 9
  • jq-devel as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in jq, a command line JSON processor. Embedded NUL bytes in import paths are truncated during module and data-file lookup, creating a mismatch between the intended import string and the actual file path opened. This issue allows an attacker who can supply a crafted script to access unintended files.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-29173

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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

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.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-20Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1449jq: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann eine Schwachstelle in jq ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-015600jqlangのjqにおける複数の脆弱性

jqはコマンドラインのJSONプロセッサです。バージョン1.8.1およびそれ以前のバージョンでは、jqはjq言語レベルで埋め込まれたNULバイトをインポートパスに受け入れていましたが、その後、モジュールおよびデータファイルの検索時にC言語の文字列操作を使ってこれらのパスを解決します。これにより、ポリシーや監査コードが検証する論理的なインポート文字列と、jqが実際に開くディスク上のパスとの間に不一致が生じていました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 11 May 2026 · Last source change 13 May 2026, 14:41 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-29173
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    <= 1.8.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    <= 1.8.1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; automation-controller.src as a component of Red Hat Ansible Automation Platform 2; jq.src as a component of Red Hat Ceph Storage 4; jq as a component of Red Hat Enterprise Linux 10; jq-devel as a component of Red Hat Enterprise Linux 10; jq.src as a component of Red Hat Enterprise Linux 10; jq as a component of Red Hat Enterprise Linux 8; jq-devel as a component of Red Hat Enterprise Linux 8; jq.src as a component of Red Hat Enterprise Linux 8; jq as a component of Red Hat Enterprise Linux 9; jq-devel as a component of Red Hat Enterprise Linux 9; jq.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: jq-main@aarch64 as a component of Red Hat Hardened Images; jq-main@src as a component of Red Hat Hardened Images; jq-main@x86_64 as a component of Red Hat Hardened Images
    After
    ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2; ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2; automation-controller.src as a component of Red Hat Ansible Automation Platform 2; jq.src as a component of Red Hat Ceph Storage 4; jq as a component of Red Hat Enterprise Linux 10; jq-devel as a component of Red Hat Enterprise Linux 10; jq.src as a component of Red Hat Enterprise Linux 10; jq as a component of Red Hat Enterprise Linux 8; jq-devel as a component of Red Hat Enterprise Linux 8; jq.src as a component of Red Hat Enterprise Linux 8; jq as a component of Red Hat Enterprise Linux 9; jq-devel as a component of Red Hat Enterprise Linux 9; jq.src as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: jq-main@aarch64 as a component of Red Hat Hardened Images; jq-main@src as a component of Red Hat Hardened Images; jq-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-29173↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-7Q7G-MRQ3-PHXR↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-43895 · cve.blacktree.nl