Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
CRITICAL severity

GHSA-vjv6-gq77-3mjw

CRITICALFix: mapfish/mapfish-print#1397

GHSA-vjv6-gq77-3mjw is a critical-severity (CVSS 9.3) XML External Entity (XXE) vulnerability in org.mapfish.print:print-lib. O3 Security confirms whether GHSA-vjv6-gq77-3mjw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XXE attack in Mapfish Print

Also known asCVE-2020-15232
Published
Jul 7, 2020
Updated
Mar 13, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Mar 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected
org.mapfish.print:print-liborg.mapfish.print:print-servletorg.mapfish.print:print-standalone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A user can do to an XML External Entity (XXE) attack with the provided SDL style.

Patches

Use version >= 3.24

Workarounds

No

References

For more information

If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.mapfish.print:print-lib3.0&&< 3.243.24
Mavenorg.mapfish.print:print-servlet3.0&&< 3.243.24
Mavenorg.mapfish.print:print-standalone3.0&&< 3.243.24

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mapfish.print:print-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.mapfish.print:print-lib to 3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vjv6-gq77-3mjw is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vjv6-gq77-3mjw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vjv6-gq77-3mjw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A user can do to an XML External Entity (XXE) attack with the provided SDL style. ### Patches Use version >= 3.24 ### Workarounds No ### References * https://cwe.mitre.org/data/definitions/611.html * https://github.com/mapfish/mapfish-print/pull/1397/commits/e1d0527d13db06b2b62ca7d6afb9e97dacd67a0e ### For more information If you have any questions or comments about this advisory Comment the pull request: https://github.com/mapfish/mapfish-print/pull/1397
O3 Security · Impact-Aware SCA

Is GHSA-vjv6-gq77-3mjw in your dependencies?

O3 detects GHSA-vjv6-gq77-3mjw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-vjv6-gq77-3mjw: XXE attack in Mapfish… | O3 Security