Quick answers
- Is CVE-2025-53648 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-53648 being exploited in the wild.
- How severe is CVE-2025-53648?
- Medium severity, with a CVSS score of 5.4, published 30 June 2026.
- Which products and versions are affected?
- Apache Software Foundation Gravitino 0.5.0 to 1.0.0; org.apache.gravitino:catalog-jdbc-common (Maven) >= 0.5.0, < 1.0.0, ECOSYSTEM:introduced=0.5.0,fixed=1.0.0.
- Is there a fix for CVE-2025-53648?
- Yes. org.apache.gravitino:catalog-jdbc-common (Maven): upgrade to 1.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-53648 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-53648?
- Check whether you run Apache Software Foundation Gravitino or org.apache.gravitino:catalog-jdbc-common (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.gravitino:catalog-jdbc-common (Maven): upgrade to 1.0.0 or later
# set org.apache.gravitino:catalog-jdbc-common to 1.0.0 in your pom.xml or build.gradle
Technical details
A SQL injection vulnerability (CWE-89) exists in the Apache Gravitino UI due to a misconfiguration in the SQL command handling. The flaw is located within the catalog-jdbc-common component. An attacker with access to the UI can exploit this to perform unauthorized file operations, specifically reading or truncating files on the host system. The vulnerability affects versions 0.5.0 up to 1.0.0. Users are advised to upgrade to version 1.0.0 or later to remediate the issue.
Affected products
- Apache Software Foundation Apache Gravitino 0.5.0 to 1.0.0
Identifiers
- CVE-2025-53648
- GHSA-7ph3-grqh-pv9v
Timeline
- 2026-06-30: disclosed
- 2026-06-30: patched: Fixed in version 1.0.0