Quick answers
- Is CVE-2025-48977 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-48977 being exploited in the wild.
- How severe is CVE-2025-48977?
- Medium severity, with a CVSS score of 6.5, published 28 May 2026.
- Which products and versions are affected?
- Apache Ignite 2.0.0 through 2.17.0; org.apache.ignite:ignite-core (Maven) >= 2.0.0, < 2.18.0, ECOSYSTEM:introduced=2.0.0,fixed=2.18.0.
- Is there a fix for CVE-2025-48977?
- Yes. org.apache.ignite:ignite-core (Maven): upgrade to 2.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-48977 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-48977?
- Check whether you run Apache Ignite or org.apache.ignite:ignite-core (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.ignite:ignite-core (Maven): upgrade to 2.18.0 or later
# set org.apache.ignite:ignite-core to 2.18.0 in your pom.xml or build.gradle
Technical details
A relative path traversal vulnerability exists in the Apache Ignite REST API within the 'cmd=log' command handler. The root cause is insufficient validation of the log path parameter; the application previously only checked if a path started with the Ignite home directory, which could be bypassed using '../' sequences. An authenticated attacker can exploit this by sending a specially crafted REST request to access files outside of the intended directory. This issue affects versions 2.0.0 through 2.17.0 and is resolved in version 2.18.0.
Affected products
- Apache Ignite 2.0.0 through 2.17.0
Identifiers
- CVE-2025-48977
- GHSA-v45h-mqf4-6939
Timeline
- 2026-05-28: disclosed
- 2026-05-28: advisory
- 2026-05-28: patched: Fixed in version 2.18.0