Skip to main content
VulnerabilityPublished Updated

CVE-2024-10572: h2oai/h2o-3 · Code Injection

Affects h2oai/h2o-3Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubh2oai/h2o-3pkg:github/h2oai/h2o-3Other threatsAffected
  • =3.46.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict network access to the `run_tool` command interface by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only.
  2. Monitor logs for unusual activity related to the `water.tools` package and unexpected file writes or server shutdown events.
  3. Employ application-layer access controls or authentication proxies to prevent unauthorized invocation of the `run_tool` command.
  4. Disable or remove the `XGBoostLibExtractTool` class exposure if feasible until a patch is released.
  5. Regularly check for official patches or updates from h2oai and apply them promptly once available.
  6. Conduct internal audits of h2o-3 deployments to identify exposed instances and remediate accordingly.
  7. Implement resource usage monitoring and alerting to detect abnormal file system usage or process terminations.
  8. Educate operational teams about this vulnerability and establish incident response plans for potential DoS events related to h2o-3.

Description

In h2oai/h2o-3 version 3.46.0.1, the `run_tool` command exposes classes in the `water.tools` package through the `ast` parser. This includes the `XGBoostLibExtractTool` class, which can be exploited to shut down the server and write large files to arbitrary directories, leading to a denial of service.

References

Community reviews

Loading reviews…