dbcve.org
IgniteApplication · Apache

CVE-2025-48977

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 2.18.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
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.

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 · high confidence

Authenticated users of Apache Ignite's REST API can exploit a relative path traversal vulnerability via the 'cmd=log' parameter. By using path traversal sequences (e.g., ../../../'), attackers can read arbitrary files on the server's filesystem that the process has read access to. The vulnerability affects versions 2.0.0 through 2.17.0.

MitigationUpgrade to Apache Ignite 2.18.0. If immediate upgrading is not feasible, restrict or disable the REST API and ensure network access is limited to trusted users only.

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
IgniteApplication
Affected:>= 2.0.0, < 2.18.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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Apache Ignite installation and version
    Locate the Apache Ignite installation and determine the installed version (e.g., check ignition version file, startup scripts, or the ignite/libs directory). Compare your version to the affected range 2.0.0 through 2.17.0.
    Affected if The installed version is 2.0.0 or higher but lower than 2.18.0
  2. Confirm REST API is enabled
    Examine the Apache Ignite configuration files (e.g., default-config.xml, ignite.xml, or startup parameters) for REST API configuration settings such as 'ConnectorConfiguration' or 'restEnabled' flags.
    Affected if The REST API is enabled in the configuration
  3. Verify 'cmd=log' endpoint accessibility
    Check if the /ignite?cmd=log endpoint is reachable by attempting a local request or reviewing network listener configurations for REST port exposure (default port 8080).
    Affected if The REST API is exposed and accessible on a network port
  4. Check authentication settings for REST endpoints
    Review the authentication configuration for the REST API to determine if anonymous or unauthenticated access is permitted.
    Affected if Authenticated users can access the REST API and the 'cmd=log' functionality

You are affected if Apache Ignite version 2.0.0 through 2.17.0 is running with the REST API enabled, allowing authenticated users to access the 'cmd=log' endpoint via network.

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 2.18.0 or later
Fixed in 2.18.0
Interim mitigation

Upgrade to Apache Ignite 2.18.0. If immediate upgrading is not feasible, restrict or disable the REST API and ensure network access is limited to trusted users only.

Recommended fix High confidence

2.18.0

  1. 1. Backup your current Apache Ignite installation, including configuration files and any persistent data.
  2. 2. Stop the Apache Ignite service to ensure a clean upgrade process.
  3. 3. Download Apache Ignite version 2.18.0 from the official Apache Ignite downloads page (https://ignite.apache.org/download).
  4. 4. Install or extract version 2.18.0 to replace the existing installation.
  5. 5. Restore your configuration files from the backup to the new installation.
  6. 6. Start the Apache Ignite service and verify it runs without errors.
  7. 7. Test that the REST API functions correctly, particularly the logging endpoint to confirm the vulnerability is resolved.
Caveat Review release notes for 2.18.0 for any configuration or API changes that may affect your deployment

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

Fix this in Ignite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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