Cyber Resilience

CVE-2025-46822

Path Traversal

Published
21 May 2025
Modified
17 June 2026
CVSS Score v4 7.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.041 90th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2025-46822 is a high-severity Absolute Path Traversal (CWE-36) vulnerability. Its CVSS base score is 7.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 10% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-46822 affects the OsamaTaher/Java-springboot-codebase, a repository of Java and Spring Boot code examples and projects. The flaw stems from insufficient path traversal protections that permit absolute path traversal, enabling unauthorized access to sensitive internal files. It is tracked under CWE-36 and carries a CVSS 4.0 score of 7.7 reflecting network-reachable exploitation without authentication or user interaction.

An unauthenticated remote attacker can supply crafted paths to read arbitrary files on the server, exposing configuration data, source code, or other sensitive material stored within the application environment. The vulnerability exists in versions prior to commit c835c6f7799eacada4c0fc77e0816f250af01ad2.

The project’s GitHub security advisory GHSA-q6mm-cm37-w637 and the referenced commit document the patch that restores proper path validation. Exploitation probability rose from a low baseline to a peak EPSS score of 0.1148 on 2025-12-11 before receding to the current value of 0.0684, indicating increased interest after public disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

OsamaTaher/Java-springboot-codebase is a collection of Java and Spring Boot code snippets, applications, and projects. Prior to commit c835c6f7799eacada4c0fc77e0816f250af01ad2, insufficient path traversal mechanisms make absolute path traversal possible. This vulnerability allows unauthorized access to sensitive internal files. Commit c835c6f7799eacada4c0fc77e0816f250af01ad2 contains a…

more

patch for the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-21323Shared CWE-36
CVE-2026-13189Shared CWE-36
CVE-2026-32997Shared CWE-36
CVE-2024-57966Shared CWE-36
CVE-2026-54202Shared CWE-36
CVE-2024-8501Shared CWE-36
CVE-2025-5927Shared CWE-36
CVE-2025-9259Shared CWE-36
CVE-2025-57790Shared CWE-36
CVE-2024-48248Shared CWE-36

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly stops construction of absolute paths from untrusted data before they reach file operations.

Enforced access authorizations can limit which resources are reachable even if a traversal succeeds.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent absolute path traversal.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect absolute path traversal via static analysis and fuzzing.

prevents

Secure development lifecycle includes input validation and path-handling requirements that reduce absolute path traversal risk.

prevents

Application security requirements typically mandate controls against path traversal in file-access functions.

prevents

Secure architecture principles call for canonicalization and sandboxing that limit absolute path traversal.

prevents

Secure coding standards directly require neutralization of absolute path sequences in pathname construction.

mitigates

Information access restriction limits which files can be reached but does not address the path-construction flaw itself.

References