{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.ignite:ignite-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48977 in the wild and no public exploit code.","fix":"Upgrade org.apache.ignite:ignite-core to 2.18.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-48977 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-48977 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.ignite:ignite-core (Maven): affected from 2.0.0; fixed in 2.18.0\n- org.apache.ignite:ignite-core (Maven): affected from 2.0.0; fixed in 2.18.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-48977/ (Markdown: https://insights.sbomify.com/CVE-2025-48977/index.md)","id":"CVE-2025-48977","markdown":"https://insights.sbomify.com/CVE-2025-48977/index.md","name":"CVE-2025-48977","record":{"aliases":["GHSA-v45h-mqf4-6939","MINI-4rpr-v3j5-wf4w","MINI-c3w7-56h3-8g44"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Ignite","requires_auth":"low_privilege","summary":"Authenticated users can read arbitrary files on the server via a path traversal flaw in the Apache Ignite REST API.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"ignite","vendor":"apache"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-23","name":"Relative Path Traversal"}],"description":"Relative Path Traversal vulnerability in Apache Ignite REST API.\n\nAuthenticated REST API users can read any file on the server with \"cmd=log\" command and a log path crafted in a certain way.\nThis issue affects Apache Ignite: from 2.0.0 through 2.17.0.\n\nUsers are recommended to upgrade to version 2.18.0, which fixes the issue.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Ignite: REST HTTP arbitrary file read vulnerability","id":"CVE-2025-48977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Command injection in EdgeMAX EdgeSwitch","id":"CVE-2025-48978"},"packages":[{"ecosystem":"Maven","fixed":["2.18.0"],"introduced":["2.0.0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":null,"source":"GHSA-v45h-mqf4-6939"},{"ecosystem":"Maven","fixed":["2.18.0"],"introduced":["2.0.0"],"last_affected":[],"package":"org.apache.ignite:ignite-core","purl":"pkg:maven/org.apache.ignite/ignite-core","source":"GHSA-v45h-mqf4-6939"}],"prev":{"headline":"Apache Commons FileUpload, Apache Commons FileUpload: FileUpload DoS via part headers","id":"CVE-2025-48976"},"products":["Apache Ignite"],"published":"2026-05-28","related":[{"cvss_score":9.8,"headline":"VMware Tanzu Spring Data Commons Property Binder","id":"CVE-2018-1273","kev_date_added":"2022-03-25","published":"2018-04-11"},{"cvss_score":9.8,"headline":"Code execution via deserialization in org.apache.ignite:ignite-core","id":"CVE-2018-8018","kev_date_added":null,"published":"2018-07-19"},{"cvss_score":9.8,"headline":"Apache serialization mechanism does not have a list of classes allowed for serialization/deserialization","id":"CVE-2018-1295","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":9.5,"headline":"Apache Ignite: Possible RCE when deserializing incoming messages by the server node","id":"CVE-2024-52577","kev_date_added":null,"published":"2025-02-14"},{"cvss_score":9.1,"headline":"File system access via H2 in Apache Ignite","id":"CVE-2020-1963","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":7.5,"headline":"Apache Ignite communicates to an external PHP server where sensitive information is sent","id":"CVE-2017-7686","kev_date_added":null,"published":"2017-06-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["Apache Software Foundation"]},"summary":"Authenticated users can read arbitrary files on the server via a path traversal flaw in the Apache Ignite REST API.","url":"https://insights.sbomify.com/CVE-2025-48977/"}