CVE-2026-61570 high CVSS 7.5

XXE (XML External Entity) in net.sf.mpxj:mpxj (CVE-2026-61570)

Summary

Vulnerability in net.sf.mpxj:mpxj (CVE-2026-61570). Confidential information can be exposed externally. Mitigation: upgrade to 16.4.1 or later.

Original description

The description as published by the source.

Impact

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

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61570 has been found in net.sf.mpxj:mpxj.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade net.sf.mpxj:mpxj to 16.4.1 or later.
If unsure, ask your IT team or search "net.sf.mpxj:mpxj CVE-2026-61570" on the vendor's site.

CVE-2026-61570 (net.sf.mpxj:mpxj) — CWE-611 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 16.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-611) exists in net.sf.mpxj:mpxj.

📍 Affected scope

Check the vendor advisory for the affected versions of net.sf.mpxj:mpxj.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 16.4.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで net.sf.mpxj:mpxj を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade net.sf.mpxj:mpxj to 16.4.1
```
ステージング環境で 16.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。