Categories
CVE-2026-44672

Code Injection in org.mapfish.print:print-lib (CVE-2026-44672)

Summary

Code injection in org.mapfish.print:print-lib (CVE-2026-44672). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.0.3 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44672 has been found in org.mapfish.print:print-lib.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.mapfish.print:print-lib to 4.0.3 or later.
If unsure, ask your IT team or search "org.mapfish.print:print-lib CVE-2026-44672" on the vendor's site.

CVE-2026-44672 (org.mapfish.print:print-lib) — CWE-94
Patched: 4.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in org.mapfish.print:print-lib.

📍 Affected scope

Check the vendor advisory for the affected versions of org.mapfish.print:print-lib.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.0.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.mapfish.print:print-lib を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade org.mapfish.print:print-lib to 4.0.3

    ステージング環境で 4.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.mapfish.print:print-lib
[{"type":"ECOSYSTEM","events":[{"introduced":"3.34.0"},{"fixed":"4.0.3"}]}]
maven org.mapfish.print:print-servlet
[{"type":"ECOSYSTEM","events":[{"introduced":"3.34.0"},{"fixed":"4.0.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details