dbcve.org
HiveApplication · Apache

CVE-2025-62728

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
SQL injection vulnerability in Hive Metastore Server (HMS) when processing delete column statistics requests via the Thrift APIs. The vulnerability is only exploitable by trusted/authorized users/applications that are allowed to call directly the Thrift APIs. In most real-world deployments, HMS is accessible to only a handful of applications (e.g., Hiveserver2) thus the vulnerability is not exploitable. Moreover, the vulnerable code cannot be reached when metastore.try.direct.sql property is set to false. This issue affects Apache Hive: from 4.1.0 before 4.2.0. Users are recommended to upgrade to version 4.2.0, which fixes the issue. Users who cannot upgrade directly are encouraged to set metastore.try.direct.sql property to false if the HMS Thrift APIs are exposed to general public.

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

SQL injection vulnerability in Apache Hive Metastore Server (HMS) when processing delete column statistics requests via Thrift APIs. The vulnerability allows authorized users who can directly call the HMS Thrift APIs to inject malicious SQL through the statistics deletion functionality. The vulnerable code path is only reachable when the metastore.try.direct.sql property is set to true (the default).

MitigationUpgrade to Apache Hive 4.2.0 or later. Alternatively, if upgrading is not feasible, set the metastore.try.direct.sql property to false to disable the vulnerable code path.

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
HiveApplication
Affected:= 4.1.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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 Hive Metastore Server version
    Run 'hive --version' or check the Hive installation directory for the version file. Alternatively, query the HMS Thrift API for its version information.
    Affected if The installed version is exactly 4.1.0
  2. Locate the HMS configuration file
    Find the hive-site.xml file used by your Hive Metastore Server, typically in $HIVE_HOME/conf/ or /etc/hive/conf/
    Affected if Configuration file exists and is in use by the HMS instance
  3. Check metastore.try.direct.sql setting
    In hive-site.xml, search for the property 'metastore.try.direct.sql' and note its value. If not present, the default is true.
    Affected if The property is set to 'true' or is absent (defaults to true)
  4. Verify HMS Thrift API accessibility
    Confirm that the Hive Metastore Server is running and accepting Thrift connections. Check if port 9083 (default HMS Thrift port) is listening.
    Affected if HMS Thrift API is accessible to users who can make direct API calls

You are affected if running Apache Hive version 4.1.0 with metastore.try.direct.sql set to true (or not explicitly set to false) and users can directly call HMS Thrift APIs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apache Hive 4.2.0 or later. Alternatively, if upgrading is not feasible, set the metastore.try.direct.sql property to false to disable the vulnerable code path.

Recommended fix High confidence

Hive 4.2.0

  1. Plan and schedule an upgrade to Hive 4.2.0
  2. Review the Hive 4.2.0 release notes for any breaking changes or migration requirements
  3. Test the upgrade in a staging environment before production deployment
  4. Execute the upgrade to Hive 4.2.0 in production
  5. Verify the SQL injection vulnerability is resolved by testing HMS delete column statistics operations via Thrift APIs
Caveat Review Hive 4.2.0 release notes for breaking changes; test thoroughly in non-production first

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

Fix this in Hive Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62728 — 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-62728 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