CVE-2022-41954 is a low-severity (CVSS 3.3) Information Exposure vulnerability in net.sf.mpxj:mpxj. A fix is available for net.sf.mpxj:mpxj — see the affected versions and patch details below.
Temporary File Information Disclosure Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- 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-41954.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-41954 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
net.sf.mpxj:mpxj.NETnet.sf.mpxj.NETnet.sf.mpxj-for-csharp.NETnet.sf.mpxj-for-vb🐍mpxjReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, NuGet packages — download data is not available via public APIs for these ecosystems.
Description
MPXJ is an open source library to read and write project plans from a variety of file formats and databases. On Unix-like operating systems (not Windows or macos), MPXJ's use of File.createTempFile(..) results in temporary files being created with the permissions -rw-r--r--. This means that any other user on the system can read the contents of this file. When MPXJ is reading a schedule file which requires the creation of a temporary file or directory, a knowledgeable local user could locate these transient files while they are in use and would then be able to read the schedule being processed by MPXJ. The problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes. Users unable to upgrade may set java.io.tmpdir to a directory to which only the user running the application has access will prevent other users from accessing these temporary files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.sf.mpxj:mpxj | all versions | 10.14.1net.sf.mpxj:mpxj:10.14.1 |
| .NETNuGet | net.sf.mpxj | all versions | 10.14.1dotnet add package net.sf.mpxj --version 10.14.1 |
| .NETNuGet | net.sf.mpxj-for-csharp | all versions | 10.14.1dotnet add package net.sf.mpxj-for-csharp --version 10.14.1 |
| .NETNuGet | net.sf.mpxj-for-vb | all versions | 10.14.1dotnet add package net.sf.mpxj-for-vb --version 10.14.1 |
| 🐍PyPI | mpxj | all versions | 10.14.1pip install --upgrade 'mpxj==10.14.1' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sf.mpxj:mpxj, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.sf.mpxj:mpxj to 10.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41954 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-41954 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-41954. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-41954 in your dependencies?
O3 Security finds CVE-2022-41954 across Maven, NuGet, PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.