GHSA-jf2p-4gqj-849g
LOWTemporary File Information Disclosure vulnerability in MPXJ
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.
Blast Radius
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
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.sf.mpxj:mpxj | all versions | 10.14.1 |
| .NETNuGet | net.sf.mpxj | all versions | 10.14.1 |
| .NETNuGet | net.sf.mpxj-for-csharp | all versions | 10.14.1 |
| .NETNuGet | net.sf.mpxj-for-vb | all versions | 10.14.1 |
| 🐍PyPI | mpxj | all versions | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-jf2p-4gqj-849g 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 pinpoints whether GHSA-jf2p-4gqj-849g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jf2p-4gqj-849g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jf2p-4gqj-849g in your dependencies?
O3 detects GHSA-jf2p-4gqj-849g across Maven, NuGet, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.