CVE-2026-3960

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.0% (63rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 1.0%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A critical remote code execution vulnerability exists in the unauthenticated REST API endpoint /99/ImportSQLTable in H2O-3 version 3.46.0.9 and prior. The vulnerability arises due to insufficient security controls in the parameter blacklist mechanism, which only targets MySQL JDBC driver-specific dangerous parameters. An attacker can bypass these controls by switching the JDBC URL protocol to jdbc:postgresql: and exploiting PostgreSQL JDBC driver-specific parameters such as socketFactory and socketFactoryArg. This allows unauthenticated attackers to execute arbitrary code on the H2O-3 server with the privileges of the H2O-3 process. The issue is resolved in version 3.46.0.10.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
1.0%
EPSS %ILE
63rd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 23, 2026

Last Modified

May 19, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit.
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/6954fe04-b905-453f-8c53-205ac8377e0d
GitHub commit

commit b9ae2d3c5220 (h2oai/h2o-3)

Fix landed in h2oai/h2o-3 commit b9ae2d3c5220 — awaiting tagged release

https://github.com/h2oai/h2o-3/commit/b9ae2d3c5220db2dc53753357a783e590364d044

Affected Packages

(2 across 2 ecosystems)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
ai.h2o:h2o-core0.1.10 ... 3.8.3.4 (255 versions)
  • every version up to 3.46.0.10: fixed in 3.46.0.10
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
h2o3.10.0.10 ... 3.46.0.9 (120 versions)
  • every version up to 3.46.0.10: fixed in 3.46.0.10
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 31× 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 95 of 186 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-3960?
CVE-2026-3960 is a critical-severity vulnerability; its CVE record was published on April 23, 2026. A critical remote code execution vulnerability exists in the unauthenticated REST API endpoint /99/ImportSQLTable in H2O-3 version 3.46.0.9 and prior. The vulnerability arises due to insufficient security controls in the parameter blacklist mechanism, which only targets MySQL JDBC driver-specific…
When was the CVE record for CVE-2026-3960 published?
The CVE record for CVE-2026-3960 was published on April 23, 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 May 19, 2026; the record at its source may have been updated since.
Is CVE-2026-3960 actively exploited?
CVE-2026-3960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3960?
CVE-2026-3960 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-3960?
A fix for CVE-2026-3960 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3960

Explore →

Is Your Infrastructure Affected by CVE-2026-3960?

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

Book a Demo →Browse All CVEs