Vulnerability Database · Maven · Package report

org.mapfish.print:print-lib: vulnerability history, versions and safety

org.mapfish.print:print-lib is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 55 releases, from Jul 2020 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 H1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 28 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.mapfish.print:print-lib 3.22.0 i

Updated on 23 Oct 2026

Action needed: 3.22.0 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 52/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Not enough data

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 3.22.0 — affected i
  • Vulnerabilities on record 4 over 6 years · 2 in the last year i
  • Latest disclosure 28 Aug 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 0 i
  • Last release 81 months ago i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.mapfish.print:print-lib, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.22.0 07 Jan 2020 C1 H1 L1 BSD-2-Clause Yes Details →
3.21.0 20 Nov 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.20.3 30 Sep 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.20.2 24 Sep 2019 C1 H1 L1 BSD-2-Clause Yes Details →
2.1.5 23 Jul 2019 L1 non-standard Yes Details →
3.20.1 24 May 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.20.0 16 May 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.19.0 05 Apr 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.18.4 06 Mar 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.18.3 06 Mar 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.8 14 Feb 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.18.2 14 Feb 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.18.1 08 Feb 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.18.0 07 Feb 2019 C1 H1 L1 BSD-2-Clause Yes Details →
3.17.0 11 Dec 2018 C1 H1 L1 BSD-2-Clause Yes Details →
2.1.4 10 Dec 2018 L1 non-standard Yes Details →
2.1.3 11 Oct 2018 L1 non-standard Yes Details →
3.16.2 28 Sep 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.16.1 14 Sep 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.16.0 04 Sep 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.15.0 02 Aug 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.14.1 13 Jun 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.14.0 07 Jun 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.13.0 14 May 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.7 05 Feb 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.12.1 31 Jan 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.12.0 18 Jan 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.6 15 Jan 2018 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.5 07 Dec 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.11.3 07 Dec 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.11.2 05 Dec 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.11.1 04 Dec 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.11.0 04 Dec 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.4 24 Oct 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.3 20 Sep 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.2 11 Aug 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.1 21 Jul 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.10.0 18 Jul 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.9.0 08 May 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.8.0 13 Mar 2017 C1 H1 L1 BSD-2-Clause Yes Details →
3.7.0 24 Oct 2016 C1 H1 L1 BSD-2-Clause Yes Details →
3.6.0 14 Sep 2016 C1 H1 L1 BSD-2-Clause Yes Details →
3.5.0 13 Jun 2016 C1 H1 L1 BSD-2-Clause Yes Details →
3.4.0 18 Mar 2016 C1 H1 L1 BSD-2-Clause Yes Details →
3.3.0 22 Jan 2016 C1 H1 L1 non-standard Yes Details →
2.1.2 15 Jan 2016 L1 non-standard Yes Details →
3.2.0 19 Nov 2015 C1 H1 L1 non-standard Yes Details →
2.1.1 09 Jun 2015 L1 non-standard Yes Details →
3.1.2 02 Mar 2015 C1 H1 L1 non-standard Yes Details →
3.1.1 18 Feb 2015 C1 H1 L1 non-standard Yes Details →
3.1.0 02 Feb 2015 C1 H1 L1 non-standard Yes Details →
3.0 13 Oct 2014 C1 H1 L1 non-standard Yes Details →
2.1.0 19 Jun 2014 L1 non-standard Yes Details →
2.0.0 20 Mar 2014 L1 non-standard Yes Details →
1.2.0 18 Mar 2013 L1 non-standard Yes Details →

All 55 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.mapfish.print:print-lib

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.mapfish.print:print-lib

Is org.mapfish.print:print-lib safe to use?

Vulert records 4 vulnerabilities for org.mapfish.print:print-lib in Maven: 2 critical, 1 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.mapfish.print:print-lib's Vulert package health score?

Vulert scores org.mapfish.print:print-lib 52/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.mapfish.print:print-lib affected?

Yes. 3.22.0, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does org.mapfish.print:print-lib have?

4 vulnerabilities are recorded for org.mapfish.print:print-lib in the Maven ecosystem: 2 critical, 1 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.mapfish.print:print-lib vulnerabilities disclosed?

2 vulnerabilities were recorded for org.mapfish.print:print-lib in the last 12 months, and the oldest entry in this database dates to 07 Jul 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.mapfish.print:print-lib are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.mapfish.print:print-lib for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.mapfish.print:print-lib version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.