ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-43895

jq is a command-line JSON processor.

Published May 11, 2026 · catalog updated Jun 17, 2026 · jq is a command-line

Check if you run it

No confirmed exploitation is on record for CVE-2026-43895. EPSS is 0.15%. Act only if a listed version of jq is a command-line is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (jq is a command-line).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.15%
Remediation
Version ranges on file
Affected products
cpe jqlang/jq · stated jq

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe jqlang/jqversion unspecified
  • stated jq<= 1.8.1

How to fix CVE-2026-43895

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-43895. EPSS is 0.15%. Act only if a listed version of jq is a command-line is installed.

Which versions are affected?

Compare what you have installed with <= 1.8.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-158; CWE-20: Improper Input Validation. EPSS 0.15%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 11, 2026 · NIST NVD

    Detected

    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.

  2. Jun 17, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-43895

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-43895

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-43895

    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 str

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.