{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40164 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-40164 is a high-severity denial of service vulnerability in jqlang jq, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40164 and fix it if it is affected.\n\nWhat it is: CVE-2026-40164 is a high-severity denial of service vulnerability in jqlang jq, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40164 exists.\n\nAffected product: jqlang jq. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40164/ (Markdown: https://insights.sbomify.com/CVE-2026-40164/index.md)","id":"CVE-2026-40164","markdown":"https://insights.sbomify.com/CVE-2026-40164/index.md","name":"CVE-2026-40164","record":{"aliases":["ALPINE-CVE-2026-40164","AZL-82934","BELL-CVE-2026-40164","DEBIAN-CVE-2026-40164","ECHO-472e-db5d-af63","GHSA-wwj8-gxm6-jc29"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JSON processing library","requires_auth":"none","summary":"Attackers can cause CPU exhaustion in jq by submitting crafted JSON objects that exploit a hardcoded hash seed, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-341","name":"Predictable from Observable State"},{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-328","name":"Use of Weak Hash"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"jq: Algorithmic complexity DoS via hardcoded MurmurHash3 seed","id":"CVE-2026-40164","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"authentik: SAML NameID XML Comment Injection Enables Authentication Bypass via Identifier Truncation","id":"CVE-2026-40165"},"packages":[],"prev":{"headline":"Saltcorn has an Unauthenticated Path Traversal in sync endpoints allows arbitrary file write and directory read","id":"CVE-2026-40163"},"products":["jq"],"published":"2026-04-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["jqlang"]},"summary":"Attackers can cause CPU exhaustion in jq by submitting crafted JSON objects that exploit a hardcoded hash seed, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-40164/"}