Skip to content

← Public intelligence

Maven package

org.mapfish:print.print-servlet

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.6MavenAmendedPublished

    MapFish Print has XXE that allows reading arbitrary files of certain types

    CVE-2026-55848 · GHSA-5v29-34h8-v68r

    Affected
    • Maven org.mapfish:print.print-servlet >= 3.0.0, < 3.28.30
    Fixed in
    3.28.30· Vendor fix available
    Issue
    XXE on MapFish Print allows reading arbitrary files of certain types. Eg /etc/passwd or k8 secrets and certs. https://github.com/mapfish/mapfish-print/commit/13020c0fbc299e5f604e4e66066311c4bf04d507 Details To trigger the XXE it is required to host a remote script and dtd file. When using the Print feature its possible to send the attacker server url as url of the gml layer. The 404 not found path when using the gml Layer will expand the content of the file as path and throw a default 404 with the full content as path. PoC Host this php file somewhere as xxe.php: and beneath host this "evil.dtd" <!ENTITY % exfil "<!ENTITY &#37; error SYSTEM 'file:///xxe-exfil/%payload;'" %exfil; %error; Now send a single curl request against your mapfish print server and include your hosted poc url as gml layer url with the path attached you would like to exfil. It will exfil /var/run/secrets/kubernetes.io/serviceaccount/token (most likely your local test setup wont have it, then just replace…

    Recommended action: Upgrade to 3.28.30 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →