How severe is CVE-2025-48977?

No CVSS score has been assigned to CVE-2025-48977 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-48977?

CVE-2025-48977 affects the following packages: org.apache.ignite:ignite-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-48977?

Update org.apache.ignite:ignite-core to 2.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48977 is resolved across your whole dependency graph.

How do I detect CVE-2025-48977 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ignite:ignite-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-48977 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2025-48977 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48977 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48977?

CVE-2025-48977 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-48977?

CVE-2025-48977 is classified as CWE-23 (CWE-23). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-48977 published, and has it been updated?

CVE-2025-48977 was published on May 28, 2026 and was last updated on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-48977 — ignite-core

Fix: apache/ignite@5c42c7a

CVE-2025-48977 is a CWE-23 vulnerability in org.apache.ignite:ignite-core. A fix is available for org.apache.ignite:ignite-core — see the affected versions and patch details below.

Apache Ignite: REST HTTP arbitrary file read vulnerability

Also known asGHSA-v45h-mqf4-6939

Published

May 28, 2026

Updated

Oct 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48977.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.ignite:ignite-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.ignite:ignite-core`	≥ 2.0.0&&< 2.18.0	2.18.0`org.apache.ignite:ignite-core:2.18.0`

Affected Products

1 product · 1 configurations

Application

igniteapache

≥ 2.0.0 && < 2.18.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ignite:ignite-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.ignite:ignite-core to 2.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48977 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2025-48977 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works