CVE-2025-10769
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 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.
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 confidenceA deserialization vulnerability exists in h2o-3's H2 JDBC Driver ImportSQLTable functionality. The connection_url parameter is not properly validated before deserialization, allowing remote attackers to potentially execute arbitrary code by supplying malicious serialized objects.
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>= 3.0.0.2, <= 3.46.0.8CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 H2O installation and versionLocate the h2o-3 jar file or installation directory, then determine the exact version number by inspecting the jar filename, manifest file (META-INF/MANIFEST.MF inside the h2o.jar), or version metadata in your deployment systemAffected if The installed version falls within the range >= 3.0.0.2 and <= 3.46.0.8
-
Verify H2 JDBC driver is loadedCheck running processes or application configuration for the presence of the H2 JDBC driver (h2*.jar) and confirm it is being used by the H2O application. Look for JDBC connection strings beginning with jdbc:h2:Affected if The H2 JDBC driver is present and loaded by the H2O service
-
Confirm ImportSQLTable functionality is exposedInspect the H2O web service endpoints or API routes for /99/ImportSQLTable or similar SQL table import functionality. Check if the ImportSQLTable feature is enabled in the H2O configurationAffected if The ImportSQLTable endpoint is accessible or the feature is enabled in configuration
-
Assess network exposure of the serviceReview firewall rules, network ACLs, and service binding configurations to determine if the H2O web interface (typically on port 54321 or similar) is exposed to untrusted networksAffected if The H2O service is reachable from network segments that contain untrusted or external users
You are affected if your H2O version is between 3.0.0.2 and 3.46.0.8, the H2 JDBC driver is loaded, and the ImportSQLTable endpoint is accessible to potentially malicious network actors.
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 dataApply any available vendor patch for h2o-3; if no patch exists, implement network-level access controls to restrict the /99/ImportSQLTable endpoint and consider disabling the H2 JDBC driver's SQL table import feature until a fix is available.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10769 — 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-2025-10769 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