# CVE-2025-10768: h2oai h2o-3 IBMDB2 JDBC Driver ImportSQLTable deserialization

> Remote attackers can achieve code execution via unsafe deserialization in the h2o-3 IBMDB2 JDBC Driver ImportSQLTable function.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-3qm2-4r9g-fg69

## What is CVE-2025-10768?

CVE-2025-10768 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.

### Official description

A flaw has been found in h2oai h2o-3 up to 3.46.08. The impacted element is an unknown function of the file /99/ImportSQLTable of the component IBMDB2 JDBC Driver. This manipulation of the argument connection_url causes deserialization. The attack may be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-10768?

It affects 1 product.


Products: H2o H2o.

## How do I fix CVE-2025-10768?

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

## Is CVE-2025-10768 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10768 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-2025-10768 and fix it if it is affected.

What it is: CVE-2025-10768 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10768 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-2025-10768/ (Markdown: https://insights.sbomify.com/CVE-2025-10768/index.md)
```

## Sources

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

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