dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-5662

CRITICAL · 9.8 CVSS v3.0 Published 2025-09-02
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
A deserialization vulnerability exists in the H2O-3 REST API (POST /99/ImportSQLTable) that affects all versions up to 3.46.0.7. This vulnerability allows remote code execution (RCE) due to improper validation of JDBC connection parameters when using a Key-Value format. The vulnerability is present in the MySQL JDBC Driver version 8.0.19 and JDK version 8u112. The issue is resolved in version 3.46.0.8.

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 · high confidence

A deserialization vulnerability in H2O-3's REST API (POST /99/ImportSQLTable) allows remote code execution due to improper validation of JDBC connection parameters in Key-Value format. The vulnerability affects all versions up to 3.46.0.7 and is tied to the MySQL JDBC Driver 8.0.19 and JDK 8u112 deserialization handling.

MitigationUpgrade H2O-3 to version 3.46.0.8 or later to address the deserialization vulnerability in the SQL table import functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed H2O-3 version
    Query the H2O-3 REST API endpoint GET /3/Version or check the h2o.jar filename/manifest
    Affected if version is 3.46.0.7 or earlier
  2. Verify SQL Import feature is accessible
    Confirm the /99/ImportSQLTable REST endpoint is available and accepts POST requests on the H2O-3 server
    Affected if the endpoint is reachable and responds to requests
  3. Check MySQL JDBC driver version
    Inspect the MySQL connector JAR file bundled with or used by H2O-3 (commonly mysql-connector-java.jar)
    Affected if driver version is 8.0.19
  4. Check Java JDK version running H2O-3
    Execute java -version on the host running H2O-3
    Affected if JDK version is 8u112 or earlier

Environment is affected if H2O-3 version is 3.46.0.7 or earlier AND the SQL Import endpoint is accessible, regardless of JDBC driver or JDK version present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade H2O-3 to version 3.46.0.8 or later to address the deserialization vulnerability in the SQL table import functionality.

Recommended fix High confidence

3.46.0.8

  1. Stop the H2O-3 service to ensure a clean upgrade process
  2. Back up the current H2O-3 installation including all configuration files and data
  3. Download H2O-3 version 3.46.0.8 from the official H2O-3 repository or release channel
  4. Replace the existing H2O-3 installation files with the new version 3.46.0.8 files
  5. Restore any custom configuration files from the backup if needed
  6. Verify the integrity of the installation by checking the version number matches 3.46.0.8
  7. Start the H2O-3 service
  8. Confirm the service is running and accessible via the REST API

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5662 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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