Improper Validation of Specified Type of Input Affecting jq package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.01% (3rd 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-16083389
  • published16 Apr 2026
  • disclosed13 Apr 2026

Introduced: 13 Apr 2026

NewCVE-2026-39956  (opens in a new tab)
CWE-1287  (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 commits after 69785bf77f86e2ea1b4a20ca86775916889e91c9, the _strindices builtin in jq's src/builtin.c passes its arguments directly to jv_string_indexes() without verifying they are strings, and jv_string_indexes() in src/jv.c relies solely on assert() checks that are stripped in release builds compiled with -DNDEBUG. This allows an attacker to crash jq trivially with input like _strindices(0), and by crafting a numeric value whose IEEE-754 bit pattern maps to a chosen pointer, achieve a controlled pointer dereference and limited memory read/probe primitive. Any deployment that evaluates untrusted jq filters against a release build is vulnerable. This issue has been patched in commit fdf8ef0f0810e3d365cdd5160de43db46f57ed03.

CVSS Base Scores

version 3.1