# CVE-2025-48977: Apache Ignite: REST HTTP arbitrary file read vulnerability

> Authenticated users can read arbitrary files on the server via a path traversal flaw in the Apache Ignite REST API.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-v45h-mqf4-6939, MINI-4rpr-v3j5-wf4w, MINI-c3w7-56h3-8g44

## What is CVE-2025-48977?

CVE-2025-48977 is a high-severity path traversal vulnerability in Apache Ignite, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Relative Path Traversal vulnerability in Apache Ignite REST API.

Authenticated REST API users can read any file on the server with "cmd=log" command and a log path crafted in a certain way.
This issue affects Apache Ignite: from 2.0.0 through 2.17.0.

Users are recommended to upgrade to version 2.18.0, which fixes the issue.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-48977?

2 open source packages ship an affected version, including org.apache.ignite:ignite-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.ignite:ignite-core` | Maven | From 2.0.0 | 2.18.0 |
| `org.apache.ignite:ignite-core` | Maven | From 2.0.0 | 2.18.0 |

Products: Apache Ignite.

## How do I fix CVE-2025-48977?

Upgrade org.apache.ignite:ignite-core to 2.18.0 or later.

## Is CVE-2025-48977 being exploited?

There is no known exploitation of CVE-2025-48977 in the wild and no public exploit code.

## Other vulnerabilities in Apache Ignite

- [CVE-2018-1273](https://insights.sbomify.com/CVE-2018-1273/): VMware Tanzu Spring Data Commons Property Binder (critical 9.8, exploited in the wild)
- [CVE-2018-8018](https://insights.sbomify.com/CVE-2018-8018/): Code execution via deserialization in org.apache.ignite:ignite-core (critical 9.8)
- [CVE-2018-1295](https://insights.sbomify.com/CVE-2018-1295/): Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization (critical 9.8)
- [CVE-2024-52577](https://insights.sbomify.com/CVE-2024-52577/): Apache Ignite: Possible RCE when deserializing incoming messages by the server node (critical 9.5)
- [CVE-2020-1963](https://insights.sbomify.com/CVE-2020-1963/): File system access via H2 in Apache Ignite (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48977 and fix it if it is affected.

What it is: CVE-2025-48977 is a high-severity path traversal vulnerability in Apache Ignite, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48977 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.ignite:ignite-core (Maven): affected from 2.0.0; fixed in 2.18.0
- org.apache.ignite:ignite-core (Maven): affected from 2.0.0; fixed in 2.18.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48977/ (Markdown: https://insights.sbomify.com/CVE-2025-48977/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48977
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48977
- OSV: https://osv.dev/vulnerability/CVE-2025-48977

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48977/
Summaries are generated and may contain mistakes; the official description above is the record.