Improper Input Validation Affecting jq package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.16% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS9-JQ-16723731
  • published17 May 2026
  • disclosed11 May 2026

Introduced: 11 May 2026

CVE-2026-43895  (opens in a new tab)
CWE-20  (opens in a new tab)

How to fix?

There is no fixed version for Centos:9 jq.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jq package and not the jq package as distributed by Centos. See How to fix? for Centos:9 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1