# CVE-2026-8750: h2oai h2o-3 ImportFile API PersistNFS.java importFiles information disclosure

> Remote attackers can exploit the ImportFile API in h2o-3 to disclose sensitive information, requiring permissions but posing a data leak risk.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-2g37-rjvj-534q

## What is CVE-2026-8750?

CVE-2026-8750 is a medium-severity vulnerability in h2oai h2o-3, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in h2oai h2o-3 up to 7402. Affected by this issue is the function importFiles of the file h2o-core/src/main/java/water/persist/PersistNFS.java of the component ImportFile API. Such manipulation leads to information disclosure. The attack can be executed remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-8750?

It affects 1 product.


Products: H2o H2o.

## How do I fix CVE-2026-8750?

No fix has been published for CVE-2026-8750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8750 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8750 exists.

## Other vulnerabilities in h2oai h2o-3

- [CVE-2023-6016](https://insights.sbomify.com/CVE-2023-6016/): H2O Remote Code Execution via POJO Model Import (critical 10.0)
- [CVE-2025-6544](https://insights.sbomify.com/CVE-2025-6544/): Deserialization Vulnerability in h2oai/h2o-3 (critical 9.8)
- [CVE-2024-10553](https://insights.sbomify.com/CVE-2024-10553/): Jdbc Deserialization in h2oai/h2o-3 (critical 9.8)
- [CVE-2023-6569](https://insights.sbomify.com/CVE-2023-6569/): External Control of File Name or Path in h2oai/h2o-3 (critical 9.3)
- [CVE-2023-6013](https://insights.sbomify.com/CVE-2023-6013/): H2O Local File Include (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8750 and fix it if it is affected.

What it is: CVE-2026-8750 is a medium-severity vulnerability in h2oai h2o-3, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8750 exists.

Affected product: h2oai h2o-3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8750/ (Markdown: https://insights.sbomify.com/CVE-2026-8750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8750
- OSV: https://osv.dev/vulnerability/CVE-2026-8750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8750/
Summaries are generated and may contain mistakes; the official description above is the record.