mapfish-print is a component of MapFish for printing templated cartographic maps. Prior to 3.28.30, 3.30.32, 3.31.24, 3.33.16, and 4.0.5, MapFish Print accepts an attacker-controlled GML layer url in requests to the /api/print3/print endpoint and fetches XML parsed by core/src/main/java/org/mapfish/print/map/geotools/GmlLayer.java without disabling external entities and external DTDs. A remote XML document and DTD can expand a local file entity, and the resulting content can be exposed through the GML parsing and error path. This allows unauthenticated attackers to read files such as operating-system account data, Kubernetes service-account tokens, and certificates. Replacing the file entity target with an internal HTTP endpoint also permits server-side request forgery. This issue is fixed in versions 3.28.30, 3.30.32, 3.31.24, 3.33.16, and 4.0.5.
CVE-2026-55848
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(low)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (10)
Auto-updated Aug 28, 2026commit 3525e8150fcb (mapfish/mapfish-print)
Fix landed in mapfish/mapfish-print commit 3525e8150fcb — awaiting tagged release
https://github.com/mapfish/mapfish-print/commit/3525e8150fcb5f40095930ccf7aec0d8ce92bbcbcommit 23a96e7baa15 (mapfish/mapfish-print)
Fix landed in mapfish/mapfish-print commit 23a96e7baa15 — awaiting tagged release
https://github.com/mapfish/mapfish-print/commit/23a96e7baa15077bdb0e5fc5a72b18da23af9121commit 13beae7a7f97 (mapfish/mapfish-print)
Fix landed in mapfish/mapfish-print commit 13beae7a7f97 — awaiting tagged release
https://github.com/mapfish/mapfish-print/commit/13beae7a7f970fc3526c1f7ca5db817d8d51fbec[Backport 3.28] [Backport 3.30] Harden the code, see commits
Fix merged in mapfish/mapfish-print PR #4221 on 2026-06-05 — awaiting tagged release
https://github.com/mapfish/mapfish-print/pull/4221[Backport 3.30] Harden the code, see commits
Fix merged in mapfish/mapfish-print PR #4219 on 2026-06-05 — awaiting tagged release
https://github.com/mapfish/mapfish-print/pull/4219[Backport 3.33] Harden the code, see commits
Fix merged in mapfish/mapfish-print PR #4217 on 2026-06-05 — awaiting tagged release
https://github.com/mapfish/mapfish-print/pull/4217[Backport 3.31] Harden the code, see commits
Fix merged in mapfish/mapfish-print PR #4216 on 2026-06-05 — awaiting tagged release
https://github.com/mapfish/mapfish-print/pull/4216[Backport 4.0] Harden the code, see commits
Fix merged in mapfish/mapfish-print PR #4215 on 2026-06-05 — awaiting tagged release
https://github.com/mapfish/mapfish-print/pull/4215Harden the code, see commits
Fix merged in mapfish/mapfish-print PR #4212 on 2026-06-04 — awaiting tagged release
https://github.com/mapfish/mapfish-print/pull/4212XXE on MapFish Print allows reading arbitrary files of certain types · Advisory · mapfish/mapfish-print · GitHub
https://github.com/mapfish/mapfish-print/security/advisories/GHSA-5v29-34h8-v68rVendor Advisories for CVE-2026-55848(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 23:25 UTCEG score recompute
- 2026-08-28 22:39 UTCEG score recompute
- 2026-08-28 22:38 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-55848?
When was CVE-2026-55848 disclosed?
Is CVE-2026-55848 actively exploited?
What is the CVSS score of CVE-2026-55848?
How do I remediate CVE-2026-55848?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55848
Is Your Infrastructure Affected by CVE-2026-55848?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.