jq: Algorithmic complexity DoS via hardcoded MurmurHash3 seed
21Vexday Risk Score
Sem sinal de exploração. Nenhum artefato público de exploração conhecido até agora.
ssvc Trackcvss 7.5epss 0.4%
probabilidade de exploração
0.4%top 71% das CVEs
exploração observada
nãonenhuma fonte reporta
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Produtos afetados
jqlang · jqReferências
https://access.redhat.com/errata/RHSA-2026:16252https://access.redhat.com/errata/RHSA-2026:16692https://access.redhat.com/errata/RHSA-2026:16693https://access.redhat.com/errata/RHSA-2026:18040https://access.redhat.com/errata/RHSA-2026:18042https://access.redhat.com/errata/RHSA-2026:18043https://access.redhat.com/errata/RHSA-2026:18044https://access.redhat.com/errata/RHSA-2026:18045https://access.redhat.com/errata/RHSA-2026:18046https://access.redhat.com/errata/RHSA-2026:18047https://access.redhat.com/errata/RHSA-2026:18048https://access.redhat.com/errata/RHSA-2026:19151