CVE-2026-8750
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn information disclosure vulnerability exists in the importFiles function of PersistNFS.java in h2o-3 up to version 7402. The ImportFile API does not properly validate or restrict file paths/inputs during NFS import operations, allowing a remote attacker to potentially access sensitive files or information beyond the intended scope. The exploit is publicly available and requires no authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 7402CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed H2o versionLocate the H2o installation and check the version number (typically found in version file, about screen, or startup logs). Compare against the affected range: version <= 7402 is vulnerable.Affected if Installed H2o version is 7402 or lower
-
Verify ImportFile API accessibilityConfirm the H2o REST API is exposed (typically on port 54321 or configured port). The ImportFile endpoint (such as /3/ImportFiles or similar NFS import endpoints) should be accessible over the network.Affected if The ImportFile API endpoint is reachable without authentication
-
Check for NFS import configurationLook for PersistNFS.java configuration files or NFS-related settings in the H2o deployment. This may appear as NFS mount configurations or import source settings in H2o's configuration directory.Affected if NFS import functionality is configured or enabled in the environment
-
Assess network exposureDetermine if the H2o web interface/API port is exposed to untrusted networks. Check firewall rules, network ACLs, and bind addresses to see if the service is accessible from outside trusted networks.Affected if The H2o service port is accessible from untrusted or public networks without authentication protection
-
Review authentication settingsExamine H2o authentication configuration to confirm whether the ImportFile API requires valid credentials. The CVE states the exploit requires no authentication.Affected if The ImportFile API does not require authentication or uses weak/no authorization controls
You are affected if H2o version is 7402 or lower AND the ImportFile API for NFS imports is accessible over the network without proper authentication or path validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and path sanitization in the importFiles function to prevent directory traversal; add authentication and authorization checks to the ImportFile API; restrict file access to intended directories only. Consider network segmentation to limit exposure until a patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8750 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data