Advisory record · GHSA-7952-gx68-cjqr

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

CVSS 5.3 MediumEPSS 0.0043 · 37th percentile

Published by the GitHub Advisory Database at 22 Sept 2026, 20:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
MPXJ.NetNuGet>=7.3.0, <16.5.016.5.0
mpxjRubyGems>=7.3.0, <16.5.016.5.0
mpxjPyPI>=7.3.0, <16.5.016.5.0
net.sf.mpxjNuGet>=7.3.0, <16.5.016.5.0
net.sf.mpxj-for-csharpNuGet>=7.3.0, <16.5.016.5.0
net.sf.mpxj-for-vbNuGet>=7.3.0, <16.5.016.5.0
net.sf.mpxj:mpxjMaven>=7.3.0, <16.5.016.5.0
Identifiers
GHSA-7952-gx68-cjqr · CVE-2026-65829 · PYSEC-2026-4108
Weakness (CWE)
CWE-22
Published
22 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

MPXJ versions 7.3.0 up to 16.5.0 (including the NuGet, RubyGems, PyPI and Maven packages of the same name) can write files to arbitrary locations when reading a specially crafted Primavera P3 PRX or SureTrak STX file. An attacker would need to supply such a file for the application to read, so the risk comes from opening files from untrusted sources. Upgrade to version 16.5.0 or later; until then, do not read PRX or STX files from untrusted sources.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 37th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:09 UTC First seen by agentprime
  2. 31 Oct 2026, 14:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.