dbcve.org
GravitinoApplication · Apache

CVE-2025-53648

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 1.0.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 misconfiguration in the Gravitino UI, in versions 1.0.0 and below, can allow a malicious user to read or truncate files. Users are recommended to upgrade to version 1.0.0, which fixes this issue.

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 confidence

SQL misconfiguration in Gravitino UI allows authenticated or low-privilege users to perform file read and truncate operations via SQL, likely through improper handling of SQL file operations like LOAD_FILE or INTO OUTFILE in the application's database queries.

MitigationUpgrade Gravitino to version 1.0.0 which contains the fix for this SQL misconfiguration.

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
GravitinoApplication
Affected:>= 0.5.0, < 1.0.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 Gravitino installation and version
    Locate the Gravitino installation directory and check the version file or run 'gravitino --version' or check the pom.xml/build.gradle if source deployment. Common paths: /opt/gravitino, /usr/local/gravitino, or the service startup script often contains version info.
    Affected if The installed version is 0.5.0 or any version >= 0.5.0 but less than 1.0.0
  2. Verify Gravitino UI is accessible
    Check if the Gravitino web UI port is open and responding. Default port is 8090. Use 'curl http://localhost:8090' or check network listeners with 'netstat -tlnp | grep 8090' or 'ss -tlnp | grep 8090'.
    Affected if The UI is accessible over network and the version is in the affected range
  3. Confirm database user privileges
    Examine the database configuration file (typically in conf/ or config/ directory, look for database connection properties in application.properties or similar). Check the database user configured for Gravitino and verify if it has elevated privileges beyond standard SELECT/INSERT/UPDATE/DELETE.
    Affected if The configured database user has privileges beyond basic DML operations, or the database configuration file shows overly permissive settings
  4. Check for SQL file operation capability
    Review database logs or audit records for recent usage of LOAD_FILE, INTO OUTFILE, or similar SQL commands that interact with the filesystem. If you have database access, test (in a non-production manner) whether the Gravitino database user can execute: SHOW VARIABLES LIKE 'secure_file_priv'; and verify if it is empty or points to a writable directory.
    Affected if The database user has FILE privilege or secure_file_priv is empty/unrestricted, allowing file system operations

You are affected if Gravitino version is 0.5.0 or higher but below 1.0.0 AND the UI is accessible AND the database user has elevated privileges or file operation capabilities.

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
Upgrade available Upgrade to 1.0.0 or later
Fixed in 1.0.0
Interim mitigation

Upgrade Gravitino to version 1.0.0 which contains the fix for this SQL misconfiguration.

Recommended fix High confidence

Gravitino 1.0.0

  1. 1. Backup your current Gravitino configuration and data.
  2. 2. Review the Gravitino 1.0.0 release notes for any migration requirements.
  3. 3. Upgrade your Gravitino installation from version 0.5.0 or later to version 1.0.0.
  4. 4. After upgrade, verify that the SQL misconfiguration has been addressed by testing file read/truncation operations through the UI.
  5. 5. Confirm normal functionality of all Gravitino services after the upgrade.
Caveat Review release notes for any breaking changes between 0.5.x-0.x versions and 1.0.0; test in staging environment first

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

Fix this in Gravitino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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