CVE-2026-44672
CVE-2026-44672 — mapfish-print: Remote Code Injection (RCE) in Dynamic table
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.
Published Updated Sources: cvelistV5, GitHub_M
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
9.3
CRITICAL
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script all four kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (3)
Products (3)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 9.3 | CVSS 4.0 | CRITICAL | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-94
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1027.006Obfuscated Files or Information: HTML Smuggling
- T1027.009Obfuscated Files or Information: Embedded Payloads
- T1564.009Hide Artifacts: Resource Forking
References
1 on the record
- github.com/mapfish/mapfish-print/security/advisories/GHSA-q7m6-wpvf-mvwx
x_refsource_CONFIRM
Elsewhere on this site
- mapfishevery CVE for this vendor
- camptocampevery CVE for this vendor
- org mapfishevery CVE for this vendor
- CWE-94other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.