{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8750 exists.","fix":"No fix has been published for CVE-2026-8750 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-8750 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8750 exists.\n\nAffected product: h2oai h2o-3. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8750/ (Markdown: https://insights.sbomify.com/CVE-2026-8750/index.md)","id":"CVE-2026-8750","markdown":"https://insights.sbomify.com/CVE-2026-8750/index.md","name":"CVE-2026-8750","record":{"aliases":["GHSA-2g37-rjvj-534q"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"h2o-3 machine learning library","requires_auth":"none","summary":"Remote attackers can exploit the ImportFile API in h2o-3 to disclose sensitive information, requiring permissions but posing a data leak risk.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"h2o","vendor":"h2o"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"h2oai h2o-3 ImportFile API PersistNFS.java importFiles information disclosure","id":"CVE-2026-8750","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"h2oai h2o-3 JAR Model.java importBinaryModel deserialization","id":"CVE-2026-8751"},"packages":[],"prev":{"headline":"Z-BlogPHP Commend Approval c_system_event.php CheckComment improper authorization","id":"CVE-2026-8747"},"products":["h2o-3"],"published":"2026-05-17","related":[{"cvss_score":10,"headline":"H2O Remote Code Execution via POJO Model Import","id":"CVE-2023-6016","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.8,"headline":"Deserialization Vulnerability in h2oai/h2o-3","id":"CVE-2025-6544","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":9.8,"headline":"Jdbc Deserialization in h2oai/h2o-3","id":"CVE-2024-10553","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.3,"headline":"External Control of File Name or Path in h2oai/h2o-3","id":"CVE-2023-6569","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":9.3,"headline":"H2O Local File Include","id":"CVE-2023-6013","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.3,"headline":"Local File Inclusion in h2oai/h2o-3","id":"CVE-2023-6038","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.1,"headline":"H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL","id":"CVE-2024-45758","kev_date_added":null,"published":"2024-09-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-18","vendors":["h2oai"]},"summary":"Remote attackers can exploit the ImportFile API in h2o-3 to disclose sensitive information, requiring permissions but posing a data leak risk.","url":"https://insights.sbomify.com/CVE-2026-8750/"}