CVE-2026-40164

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
7.5
EG Score
7.5(medium)
EPSS
28.8%
KEV
Not listed

Published

April 14, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

Algorithmic complexity DoS via hardcoded MurmurHash3 seed · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-wwj8-gxm6-jc29
github_commit

commit 0c7d133c3c7e (jqlang/jq)

Fix landed in jqlang/jq commit 0c7d133c3c7e — awaiting tagged release

https://github.com/jqlang/jq/commit/0c7d133c3c7e37c00b6d46b658a02244fdd3c784

Vendor Advisories for CVE-2026-40164(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibjq1 (1.6-1ubuntu0.20.04.1+esm3) @ focal2026-06-14ubuntu
ubuntulibjq1 (1.8.1-4ubuntu2) @ resolute2026-06-14ubuntu
ubuntulibjq1 (1.7.1-3ubuntu0.24.04.2) @ noble2026-06-14ubuntu
redhatrhcos-415.92.202606030318-02026-06-11redhat
redhatrhaiis/model-opt-cuda-rhel9:17806819842026-06-10redhat
redhatrhcos-4.19.9.6.202606031700-02026-06-10redhat
redhatjq-0:1.7.1-11.el10_2.22026-05-19redhat
redhatjq-0:1.6-19.el9_8.22026-05-19redhat
redhatjq-0:1.6-17.el9_6.42026-05-18redhat
redhatjq-0:1.6-15.el9_2.32026-05-18redhat
redhatjq-0:1.7.1-8.el10_0.32026-05-18redhat
redhatjq-0:1.6-12.el9_0.32026-05-18redhat
redhatjq-0:1.6-3.el8_6.22026-05-18redhat
redhatjq-0:1.6-16.el9_4.22026-05-18redhat
redhatjq-0:1.5-12.el8_4.52026-05-18redhat
redhatjq-0:1.6-6.el8_8.42026-05-18redhat
redhatjq-0:1.6-19.el9_7.0.22026-05-13redhat
redhatjq-0:1.7.1-11.el10_1.0.22026-05-13redhat
redhatjq-0:1.6-12.el8_102026-05-12redhat
redhatjq-main-1.8.1-3.hum12026-04-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 72 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-24 14:05 UTCEPSS rescore
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 14:56 UTCEPSS rescore
  8. 2026-06-21 01:59 UTCEPSS rescore
  9. 2026-06-19 19:25 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-18 17:52 UTCEPSS rescore
  12. 2026-06-17 17:53 UTCEPSS rescore
  13. 2026-06-16 17:52 UTCEPSS rescore
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-14 21:37 UTCVendor advisory
  16. 2026-06-13 23:00 UTCEPSS rescore
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 06:26 UTCVendor advisory
  20. 2026-06-11 19:33 UTCVendor advisory
  21. 2026-06-11 14:00 UTCEPSS rescore
  22. 2026-06-10 22:29 UTCVendor advisory
  23. 2026-06-10 22:18 UTCEPSS rescore
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-10 11:36 UTCVendor advisory
  27. 2026-06-10 00:43 UTCVendor advisory
  28. 2026-06-09 10:59 UTCVendor advisory
  29. 2026-06-08 15:04 UTCVendor advisory
  30. 2026-06-08 14:17 UTCEPSS rescore
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-08 04:11 UTCVendor advisory
  33. 2026-06-07 17:17 UTCVendor advisory
  34. 2026-06-07 15:25 UTCEPSS rescore
  35. 2026-06-07 15:25 UTCEPSS rescore
  36. 2026-06-07 06:24 UTCVendor advisory
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-06 13:47 UTCEPSS rescore
  39. 2026-06-05 22:47 UTCEPSS rescore
  40. 2026-06-05 22:47 UTCEPSS rescore
  41. 2026-06-05 06:10 UTCEPSS rescore
  42. 2026-06-05 06:10 UTCEPSS rescore
  43. 2026-06-04 13:12 UTCEPSS rescore
  44. 2026-06-04 13:12 UTCEPSS rescore
  45. 2026-06-02 20:13 UTCEPSS rescore
  46. 2026-06-02 18:59 UTCVendor advisory
  47. 2026-06-01 20:42 UTCVendor advisory
  48. 2026-06-01 13:52 UTCEPSS rescore
  49. 2026-06-01 13:52 UTCEPSS rescore
  50. 2026-06-01 13:51 UTCEPSS rescore
  51. 2026-05-31 22:30 UTCEPSS rescore
  52. 2026-05-31 22:30 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-31 00:16 UTCEPSS rescore
  55. 2026-05-31 00:16 UTCEPSS rescore
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-29 13:44 UTCEPSS rescore
  58. 2026-05-28 13:44 UTCEPSS rescore
  59. 2026-05-28 13:44 UTCEPSS rescore
  60. 2026-05-28 13:44 UTCEPSS rescore
  61. 2026-05-27 13:40 UTCEPSS rescore
  62. 2026-05-27 13:40 UTCEPSS rescore
  63. 2026-05-27 13:40 UTCEPSS rescore
  64. 2026-05-26 13:44 UTCEPSS rescore
  65. 2026-05-26 07:18 UTCEPSS rescore
  66. 2026-05-26 07:18 UTCEPSS rescore
  67. 2026-05-20 22:38 UTCEPSS rescore
  68. 2026-05-20 22:38 UTCEPSS rescore
  69. 2026-05-20 17:31 UTCEG score recompute
  70. 2026-05-20 17:31 UTCVendor advisory
  71. 2026-05-20 11:22 UTCEPSS rescore
  72. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-40164?
CVE-2026-40164 is a high vulnerability published on April 14, 2026. 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…
When was CVE-2026-40164 disclosed?
CVE-2026-40164 was first published in the National Vulnerability Database on April 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40164 actively exploited?
CVE-2026-40164 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40164?
CVE-2026-40164 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-40164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40164, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-40164

Explore →

Is Your Infrastructure Affected by CVE-2026-40164?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs