CVE-2026-65829

MPXJ: Potential Path Traversal Vulnerability in Primavera P3 PRX and SureTrak STX readers

Workarounds

Do not read PRX or STX files from untrusted sources.

When reading a suitably crafted PRX or STX file, MPXJ can be made to write files to arbitrary locations in the file system.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-65829 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (16.5.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This issue is addressed in MPXJ version 16.5.0.

1. What is CVE-2026-65829? CVE-2026-65829 is a medium-severity path traversal vulnerability in MPXJ.Net (nuget), affecting versions >= 7.3.0, < 16.5.0. It is fixed in 16.5.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-65829? CVE-2026-65829 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-65829?
   • MPXJ.Net (nuget) (versions >= 7.3.0, < 16.5.0)
   • mpxj (rubygems) (versions >= 7.3.0, < 16.5.0)
   • net.sf.mpxj (nuget) (versions >= 7.3.0, < 16.5.0)
   • net.sf.mpxj-for-csharp (nuget) (versions >= 7.3.0, < 16.5.0)
   • net.sf.mpxj-for-vb (nuget) (versions >= 7.3.0, < 16.5.0)
   • net.sf.mpxj:mpxj (maven) (versions >= 7.3.0, < 16.5.0)
4. Is there a fix for CVE-2026-65829? Yes. CVE-2026-65829 is fixed in 16.5.0. Upgrade to this version or later.
5. Is CVE-2026-65829 exploitable, and should I be worried? Whether CVE-2026-65829 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-65829 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-65829?
   • Upgrade MPXJ.Net to 16.5.0 or later
   • Upgrade mpxj to 16.5.0 or later
   • Upgrade mpxj to 16.5.0 or later
   • Upgrade net.sf.mpxj to 16.5.0 or later
   • Upgrade net.sf.mpxj-for-csharp to 16.5.0 or later
   • Upgrade net.sf.mpxj-for-vb to 16.5.0 or later
   • Upgrade net.sf.mpxj:mpxj to 16.5.0 or later

Other vulnerabilities in MPXJ.Net