Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.0amended

Temporary File Information Disclosure vulnerability in MPXJ

CVE-2022-41954GHSA-jf2p-4gqj-849g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (net.sf.mpxj 10.14.1; net.sf.mpxj:mpxj 10.14.1; net.sf.mpxj-for-vb 10.14.1; mpxj 10.14.1; net.sf.mpxj-for-csharp 10.14.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.0 · CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2022-41954: 0.21% estimated exploitation activity in the next 30 days; percentile 12.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jf2p-4gqj-849g

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-jf2p-4gqj-849g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-41954

Advisory: Temporary File Information Disclosure vulnerability in MPXJ
IDs: CVE-2022-41954, GHSA-jf2p-4gqj-849g
Record: https://patchnext.com/advisories/cve-2022-41954 (revision 3, source checked 26 Oct 2026, 13:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: net.sf.mpxj 10.14.1; net.sf.mpxj:mpxj 10.14.1; net.sf.mpxj-for-vb 10.14.1; mpxj 10.14.1; net.sf.mpxj-for-csharp 10.14.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet net.sf.mpxj: affected < 10.14.1; fixed in 10.14.1
- Maven net.sf.mpxj:mpxj: affected < 10.14.1; fixed in 10.14.1
- NuGet net.sf.mpxj-for-vb: affected < 10.14.1; fixed in 10.14.1
- PyPI mpxj: affected < 10.14.1; fixed in 10.14.1
- NuGet net.sf.mpxj-for-csharp: affected < 10.14.1; fixed in 10.14.1

## Suggested inspection (read-only)
- NuGet net.sf.mpxj: check the installed version with your package manager.
- Maven net.sf.mpxj:mpxj: check the installed version with your package manager.
- NuGet net.sf.mpxj-for-vb: check the installed version with your package manager.
- `python -m pip show mpxj`: prints the installed version. Run with the environment that serves production active.
- NuGet net.sf.mpxj-for-csharp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on net.sf.mpxj, net.sf.mpxj:mpxj, net.sf.mpxj-for-vb, mpxj, net.sf.mpxj-for-csharp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jf2p-4gqj-849g (OSV record GHSA-jf2p-4gqj-849g lists affected ranges: Maven net.sf.mpxj:mpxj >=0 =0 =0 =0 =0 <10.14.1 (fixed))
- Verified: https://github.com/advisories/GHSA-jf2p-4gqj-849g (GitHub-reviewed advisory GHSA-jf2p-4gqj-849g lists affected ranges: Maven net.sf.mpxj:mpxj >=0 =0 =0 =0 =0 <10.14.1)

Commands are suggestions: review each one before running it.

Loading voting…