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.
References
Configurations
No configuration.
History
10 Jul 2026, 12:16
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
02 Jul 2026, 12:17
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
30 Jun 2026, 03:19
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-341 | |
| References |
|
14 Apr 2026, 00:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-04-14 00:16
Updated : 2026-07-15 02:21
NVD link : CVE-2026-40164
Mitre link : CVE-2026-40164
CVE.ORG link : CVE-2026-40164
JSON object : View
Products Affected
No product.