GHSA-5VVX-3H34-F3GJ
Vulnerability from github – Published: 2026-09-22 20:34 – Updated: 2026-09-22 20:34Impact
MPXJ used the default configuration when creating a DocumentBuilder instance, which leaves doctype declarations enabled, when parsing the XML content of the ZTIMEINTERVALS column from a Merlin project SQLite file. This would allow a carefully crafted XML payload to read an arbitrary file. However, although an arbitrary file can be read, the way the resulting parsed XML is processed by MPXJ means that the data it contains is unlikely to be available for exfiltration.
Patches
The patch is included in MPXJ 16.4.1
Workarounds
Potential workarounds include: * Avoid reading Merlin project files with MPXJ * Only accept Merlin project files from trusted sources * Preprocess Merlin SQLite databases to strip doctype declarations from the ZTIMEINTERVALS column
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "net.sf.mpxj:mpxj"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "RubyGems",
"name": "mpxj"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "MPXJ.Net"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "net.sf.mpxj"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "net.sf.mpxj-for-csharp"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "net.sf.mpxj-for-vb"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "mpxj"
},
"ranges": [
{
"events": [
{
"introduced": "5.5.5"
},
{
"fixed": "16.4.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-61570"
],
"database_specific": {
"cwe_ids": [
"CWE-611"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-22T20:34:25Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "### Impact\nMPXJ used the default configuration when creating a DocumentBuilder instance, which leaves doctype declarations enabled, when parsing the XML content of the ZTIMEINTERVALS column from a Merlin project SQLite file. This would allow a carefully crafted XML payload to read an arbitrary file. However, although an arbitrary file can be read, the way the resulting parsed XML is processed by MPXJ means that the data it contains is unlikely to be available for exfiltration.\n\n### Patches\nThe patch is included in MPXJ 16.4.1\n\n### Workarounds\nPotential workarounds include:\n* Avoid reading Merlin project files with MPXJ\n* Only accept Merlin project files from trusted sources\n* Preprocess Merlin SQLite databases to strip doctype declarations from the ZTIMEINTERVALS column",
"id": "GHSA-5vvx-3h34-f3gj",
"modified": "2026-09-22T20:34:25Z",
"published": "2026-09-22T20:34:25Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/joniles/mpxj/security/advisories/GHSA-5vvx-3h34-f3gj"
},
{
"type": "WEB",
"url": "https://github.com/joniles/mpxj/commit/6e8288bc4d1cd62842af298004dc74fe66fb0805"
},
{
"type": "PACKAGE",
"url": "https://github.com/joniles/mpxj"
},
{
"type": "WEB",
"url": "https://github.com/joniles/mpxj/releases/tag/v16.4.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "MPXJ: XXE Vulnerability in MerlinReader"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.