CVE-2022-45921 — fusionauth-java-client
HIGHCVE-2022-45921 is a high-severity (CVSS 7.5) Path Traversal vulnerability in io.fusionauth:fusionauth-java-client. A fix is available for io.fusionauth:fusionauth-java-client — see the affected versions and patch details below.
FusionAuth vulnerable to directory traversal attack
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-2022-45921.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.fusionauth:fusionauth-java-clientReal-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
FusionAuth before 1.41.3 allows a file outside of the application root to be viewed or retrieved using an HTTP request. To be specific, an attacker may be able to view or retrieve any file readable by the user running the FusionAuth process.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.fusionauth:fusionauth-java-client | ≥ 1.37.0&&< 1.41.3 | 1.41.3io.fusionauth:fusionauth-java-client:1.41.3 |
Affected Products
fusionauthfusionauthDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.fusionauth:fusionauth-java-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.fusionauth:fusionauth-java-client to 1.41.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-45921 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
Is CVE-2022-45921 in your dependencies?
Find it across Maven, including transitive dependencies.