Reversible One-Way Hash Affecting libjq-devel package, versions <1.7.1-160000.3.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.37% (29th 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-SLES1600-LIBJQDEVEL-17977992
  • published15 Jul 2026
  • disclosed7 Jul 2026

Introduced: 7 Jul 2026

NewCVE-2026-40164  (opens in a new tab)
CWE-328  (opens in a new tab)
CWE-407  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 libjq-devel to version 1.7.1-160000.3.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libjq-devel package and not the libjq-devel package as distributed by SLES. See How to fix? for SLES:16.0.0 relevant fixed versions and status.

jq is a command-line JSON processor. Before commit 0c7d133c3c7e37c00b6d46b658a02244fdd3c784, jq used MurmurHash3 with a hardcoded, publicly visible seed (0x432A9843) for all JSON object hash table operations, which allowed an attacker to precompute key collisions offline. By supplying a crafted JSON object (~100 KB) where all keys hashed to the same bucket, hash table lookups degraded from O(1) to O(n), turning any jq expression into an O(n²) operation and causing significant CPU exhaustion. This affected common jq use cases such as CI/CD pipelines, web services, and data processing scripts, and was far more practical to exploit than existing heap overflow issues since it required only a small payload. This issue has been patched in commit 0c7d133c3c7e37c00b6d46b658a02244fdd3c784.

CVSS Base Scores

version 3.1