CVE-2026-40164

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 14, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibjq1 (1.6-1ubuntu0.20.04.1+esm3) @ focal2026-10-17ubuntu
ubuntulibjq1 (1.8.1-4ubuntu2) @ resolute2026-10-17ubuntu
redhatrhai/base-image-neuron-rhel9:17907035422026-10-01redhat
redhatrhcos-417.94.202606250942-02026-07-09redhat
redhatrhcos-414.92.202606231112-02026-07-01redhat
redhatrhcos-413.92.202606160406-02026-06-25redhat
redhatrhaiis/model-opt-cuda-rhel9:17823529502026-06-25redhat
redhatrhaiis/vllm-spyre-rhel9:17823529192026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatrhcos-412.86.202606140301-02026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatrhcos-416.94.202606051757-02026-06-18redhat
redhatrhcos-418.94.202606051320-02026-06-17redhat
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.6-19.el9_8.22026-05-19redhat
redhatjq-0:1.7.1-11.el10_2.22026-05-19redhat
redhatjq-0:1.6-17.el9_6.42026-05-18redhat
redhatjq-0:1.6-6.el8_8.42026-05-18redhat
redhatjq-0:1.7.1-8.el10_0.32026-05-18redhat
redhatjq-0:1.5-12.el8_4.52026-05-18redhat
redhatjq-0:1.6-3.el8_6.22026-05-18redhat
redhatjq-0:1.6-15.el9_2.32026-05-18redhat
redhatjq-0:1.6-16.el9_4.22026-05-18redhat
redhatjq-0:1.6-12.el9_0.32026-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.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
jq—
  • every version up to 1.8.2-r0: fixed in 1.8.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
jq—
  • every version up to 1.8.2-r0: fixed in 1.8.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
jq—
  • every version up to 1.8.2-r0: fixed in 1.8.2-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.6-2.1, 1.6-2.1+deb11u1
  • every version up to 1.6-2.1+deb11u2: fixed in 1.6-2.1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.6-2.1, 1.6-2.1+deb12u1
  • every version up to 1.6-2.1+deb12u2: fixed in 1.6-2.1+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.7.1-6+deb13u1
  • every version up to 1.7.1-6+deb13u2: fixed in 1.7.1-6+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.8.0-1, 1.8.1-1, 1.8.1-2, 1.8.1-3, 1.8.1-4
  • every version up to 1.8.1-5: fixed in 1.8.1-5
—

Weakness Classification(3)

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

Additional Vendor Advisories

(8)

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 227 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-40164?
CVE-2026-40164 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-40164 published?
The CVE record for CVE-2026-40164 was published on April 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-40164 actively exploited?
CVE-2026-40164 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40164?
CVE-2026-40164 has a CVSS base score of 7.5 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-40164?
A fix for CVE-2026-40164 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40164 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.