How severe is CVE-2022-41954?

CVE-2022-41954 has a CVSS score of 3.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-41954?

CVE-2022-41954 affects the following packages: net.sf.mpxj:mpxj (Maven), net.sf.mpxj (NuGet), net.sf.mpxj-for-csharp (NuGet), net.sf.mpxj-for-vb (NuGet), mpxj (PyPI). Ecosystems affected: Maven, NuGet, PyPI.

How do I fix CVE-2022-41954?

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.

How do I detect CVE-2022-41954 in my Maven, NuGet, PyPI dependencies?

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.

How do I mitigate CVE-2022-41954 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2022-41954 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-41954 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-41954?

CVE-2022-41954 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-41954?

CVE-2022-41954 is classified as Information Exposure (CWE-200), CWE-377 (CWE-377), CWE-668 (CWE-668). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-41954 published, and has it been updated?

CVE-2022-41954 was published on November 25, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven.NET NuGet🐍 PyPI

Not in CISA KEV

LOW severity

CVE-2022-41954 — mpxj

LOWFix: joniles/mpxj@ae0af24

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

Also known asGHSA-jf2p-4gqj-849gPYSEC-2022-42996

Published

Nov 25, 2022

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

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

5 pkgs affected

☕net.sf.mpxj:mpxj.NETnet.sf.mpxj.NETnet.sf.mpxj-for-csharp.NETnet.sf.mpxj-for-vb🐍mpxj

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

Impact

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

Patches

The problem has been patched, MPXJ version 10.14.1 and later includes the necessary changes.

Workarounds

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

For more information

If you have any questions or comments about this advisory

Open an issue in https://github.com/joniles/mpxj

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`net.sf.mpxj:mpxj`	all versions	10.14.1`net.sf.mpxj:mpxj:10.14.1`
.NETNuGet	`net.sf.mpxj`	all versions	10.14.1`dotnet add package net.sf.mpxj --version 10.14.1`
.NETNuGet	`net.sf.mpxj-for-csharp`	all versions	10.14.1`dotnet add package net.sf.mpxj-for-csharp --version 10.14.1`
.NETNuGet	`net.sf.mpxj-for-vb`	all versions	10.14.1`dotnet add package net.sf.mpxj-for-vb --version 10.14.1`
🐍PyPI	`mpxj`	all versions	10.14.1`pip install --upgrade 'mpxj==10.14.1'`

Affected Products

1 product · 1 configurations

Application

mpxjmpxj

< 10.14.1

range

Detection & mitigation playbook

Open-source dependency

Detect
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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact 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 type of 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. ### Patches The problem has been patched, MPXJ version 10.14.1 and later inc