dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-44672

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
mapfish-print is a component of MapFish for printing templated cartographic maps. From 3.23.0 to before 3.28.28, 3.30.30, 3.31.22, 3.33.14, and 4.0.3, the attacker can execute arbitrary code in Dynamic table without being authenticated. This vulnerability is fixed in 3.28.28, 3.30.30, 3.31.22, 3.33.14, and 4.0.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

mapfish-print, a cartographic map printing component of MapFish, contains an unauthenticated remote code execution vulnerability in its Dynamic table feature. Affected versions range from 3.23.0 through the patched releases (3.28.28, 3.30.30, 3.31.22, 3.33.14, and 4.0.3), allowing attackers to execute arbitrary code without any authentication.

MitigationUpgrade mapfish-print to one of the fixed versions (3.28.28, 3.30.30, 3.31.22, 3.33.14, or 4.0.3). If immediate patching is not feasible, restrict network access to the print service to prevent external exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify mapfish-print installation and version
    Locate the mapfish-print application in your environment (common locations: /opt/mapfish-print, war deployed in servlet container, or bundled with MapFish suite). Check version by examining pom.xml, manifest, or version file in the installation directory. Compare against affected range: 3.23.0 through versions below 3.28.28, 3.30.30, 3.31.22, 3.33.14, or 4.0.3.
    Affected if Installed version is 3.23.0 or higher but below the five fixed versions.
  2. Confirm Dynamic table feature is accessible
    Examine the mapfish-print configuration file (typically print-config.yaml or similar) to determine if the Dynamic table functionality is enabled or exposed. Also check if the print service endpoint is accessible over the network without authentication.
    Affected if Dynamic table feature is enabled and the print service accepts unauthenticated requests.
  3. Check network exposure of print service
    Verify whether the mapfish-print HTTP endpoint is exposed to untrusted networks or the public internet. Review firewall rules, reverse proxy configuration, and network ACLs controlling access to the print service port.
    Affected if The print service is reachable from untrusted networks without authentication.

You are affected if mapfish-print version is between 3.23.0 and the fixed versions AND the Dynamic table feature is enabled with the service exposed to unauthenticated access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade mapfish-print to one of the fixed versions (3.28.28, 3.30.30, 3.31.22, 3.33.14, or 4.0.3). If immediate patching is not feasible, restrict network access to the print service to prevent external exploitation.

Recommended fix High confidence

Upgrade to mapfish-print version 4.0.3 (or any of: 3.28.28, 3.30.30, 3.31.22, 3.33.14)

  1. Identify the current version of mapfish-print in use by checking project dependencies (e.g., Maven pom.xml, Gradle build.gradle, or package.json)
  2. Upgrade mapfish-print to version 3.28.28, 3.30.30, 3.31.22, 3.33.14, or 4.0.3 or later. For Maven, update the dependency version in pom.xml: <version>4.0.3</version> or the desired fixed version. For Gradle, update to implementation 'org.mapfish.print:printlib:4.0.3'. For other build systems, update accordingly
  3. After upgrading, rebuild and redeploy the application
  4. Verify the upgrade was successful and test that the Dynamic table functionality works correctly
  5. Ensure no regressions in other print functionality
Caveat Review release notes between your current version and the target version for any breaking changes or deprecations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44672 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data