{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10769 exists.","fix":"No fix has been published for CVE-2025-10769 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10769 is a medium-severity unsafe deserialization vulnerability in h2oai h2o-3, published on 21 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10769 and fix it if it is affected.\n\nWhat it is: CVE-2025-10769 is a medium-severity unsafe deserialization vulnerability in h2oai h2o-3, published on 21 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10769 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-2025-10769/ (Markdown: https://insights.sbomify.com/CVE-2025-10769/index.md)","id":"CVE-2025-10769","markdown":"https://insights.sbomify.com/CVE-2025-10769/index.md","name":"CVE-2025-10769","record":{"aliases":["GHSA-9w9w-c98p-vmpv"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"H2O-3 machine learning library","requires_auth":"low_privilege","summary":"Remote attackers can achieve code execution via unsafe deserialization in the H2 JDBC Driver's ImportSQLTable function within the H2O-3 library.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"h2o","vendor":"h2o"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A vulnerability has been found in h2oai h2o-3 up to 3.46.08. This affects an unknown function of the file /99/ImportSQLTable of the component H2 JDBC Driver. Such manipulation of the argument connection_url leads to deserialization. The attack may be launched remotely. The exploit has been disclosed to the public and may 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 H2 JDBC Driver ImportSQLTable deserialization","id":"CVE-2025-10769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"jeecgboot JimuReport MySQL JDBC testConnection deserialization","id":"CVE-2025-10770"},"packages":[],"prev":{"headline":"h2oai h2o-3 IBMDB2 JDBC Driver ImportSQLTable deserialization","id":"CVE-2025-10768"},"products":["h2o-3"],"published":"2025-09-21","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-22","vendors":["h2oai"]},"summary":"Remote attackers can achieve code execution via unsafe deserialization in the H2 JDBC Driver's ImportSQLTable function within the H2O-3 library.","url":"https://insights.sbomify.com/CVE-2025-10769/"}