mapfish mapfish-print up to 4.0.4 GML Parser GmlLayer.java url server-side request forgery

Summaryinfo

A vulnerability was found in mapfish mapfish-print up to 3.28.29/3.30.31/3.31.23/3.33.15/4.0.4. It has been classified as problematic. The impacted element is an unknown function of the file core/src/main/java/org/mapfish/print/map/geotools/GmlLayer.java of the component GML Parser. Performing a manipulation of the argument url results in server-side request forgery. This vulnerability is known as CVE-2026-55848. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in mapfish mapfish-print up to 3.28.29/3.30.31/3.31.23/3.33.15/4.0.4. This affects an unknown code block of the file core/src/main/java/org/mapfish/print/map/geotools/GmlLayer.java of the component GML Parser. The manipulation of the argument url with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-55848 since 06/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 3.28.30, 3.30.32, 3.31.24, 3.33.16 or 4.0.5 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• mapfish

Name

• mapfish-print

Version

• 3.28.0
• 3.28.1
• 3.28.2
• 3.28.3
• 3.28.4
• 3.28.5
• 3.28.6
• 3.28.7
• 3.28.8
• 3.28.9
• 3.28.10
• 3.28.11
• 3.28.12
• 3.28.13
• 3.28.14
• 3.28.15
• 3.28.16
• 3.28.17
• 3.28.18
• 3.28.19
• 3.28.20
• 3.28.21
• 3.28.22
• 3.28.23
• 3.28.24
• 3.28.25
• 3.28.26
• 3.28.27
• 3.28.28
• 3.28.29
• 3.30.0
• 3.30.1
• 3.30.2
• 3.30.3
• 3.30.4
• 3.30.5
• 3.30.6
• 3.30.7
• 3.30.8
• 3.30.9
• 3.30.10
• 3.30.11
• 3.30.12
• 3.30.13
• 3.30.14
• 3.30.15
• 3.30.16
• 3.30.17
• 3.30.18
• 3.30.19
• 3.30.20
• 3.30.21
• 3.30.22
• 3.30.23
• 3.30.24
• 3.30.25
• 3.30.26
• 3.30.27
• 3.30.28
• 3.30.29
• 3.30.30
• 3.30.31
• 3.31.0
• 3.31.1
• 3.31.2
• 3.31.3
• 3.31.4
• 3.31.5
• 3.31.6
• 3.31.7
• 3.31.8
• 3.31.9
• 3.31.10
• 3.31.11
• 3.31.12
• 3.31.13
• 3.31.14
• 3.31.15
• 3.31.16
• 3.31.17
• 3.31.18
• 3.31.19
• 3.31.20
• 3.31.21
• 3.31.22
• 3.31.23
• 3.33.0
• 3.33.1
• 3.33.2
• 3.33.3
• 3.33.4
• 3.33.5
• 3.33.6
• 3.33.7
• 3.33.8
• 3.33.9
• 3.33.10
• 3.33.11
• 3.33.12
• 3.33.13
• 3.33.14
• 3.33.15
• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 4.0.4

Website

• Product: https://github.com/mapfish/mapfish-print/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion