VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.poi:poi: vulnerability history, versions and safety

org.apache.poi:poi is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 52 releases, from Jan 2021 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H1 M6
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.poi:poi vulnerabilities

Vulert verdict on org.apache.poi:poi 6.0.0 i

Updated on 23 Oct 2026

Good news: 6.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 93/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

What to do: Stay on 6.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 6.0.0 — unaffected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Last release this month i
  • Licence Apache-2.0 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.apache.poi:poi, 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
6.0.0 19 Oct 2026 none Apache-2.0 — Details →
5.5.1 26 Nov 2025 none Apache-2.0 — Details →
5.5.0 06 Nov 2025 none Apache-2.0 — Details →
5.4.1 01 Apr 2025 none Apache-2.0 — Details →
5.4.0 29 Dec 2024 none Apache-2.0 — Details →
5.3.0 25 Jun 2024 none Apache-2.0 — Details →
5.2.5 17 Nov 2023 none Apache-2.0 — Details →
5.2.4 21 Sep 2023 none Apache-2.0 — Details →
5.2.3 09 Sep 2022 none Apache-2.0 — Details →
5.2.2 12 Mar 2022 none Apache-2.0 — Details →
5.2.1 24 Feb 2022 none Apache-2.0 — Details →
5.2.0 06 Jan 2022 none Apache-2.0 — Details →
5.1.0 25 Oct 2021 none Apache-2.0 — Details →
5.0.0 12 Jan 2021 none Apache-2.0 — Details →
4.1.2 10 Feb 2020 none Apache-2.0 — Details →
4.1.1 15 Oct 2019 none Apache-2.0 — Details →
4.1.0 05 Apr 2019 M1 Apache-2.0 Yes Details →
4.0.1 26 Nov 2018 M1 Apache-2.0 Yes Details →
4.0.0 31 Aug 2018 M1 Apache-2.0 Yes Details →
3.17 08 Sep 2017 M1 Apache-2.0 Yes Details →
3.17-beta1 24 Jun 2017 H1 M1 Apache-2.0 Yes Details →
3.16 11 Apr 2017 H1 M1 Apache-2.0 Yes Details →
3.16-beta2 27 Jan 2017 H1 M1 Apache-2.0 Yes Details →
3.16-beta1 13 Nov 2016 H1 M1 Apache-2.0 Yes Details →
3.15 17 Sep 2016 H1 M1 Apache-2.0 Yes Details →
3.15-beta2 25 Jun 2016 H1 M2 Apache-2.0 Yes Details →
3.15-beta1 15 Apr 2016 H1 M2 Apache-2.0 Yes Details →
3.14 06 Mar 2016 H1 M2 Apache-2.0 Yes Details →
3.14-beta1 24 Dec 2015 H1 M2 Apache-2.0 Yes Details →
3.13 22 Sep 2015 H1 M2 Apache-2.0 Yes Details →
3.13-beta1 19 Jul 2015 H1 M2 Apache-2.0 Yes Details →
3.12 10 May 2015 H1 M2 Apache-2.0 Yes Details →
3.12-beta1 24 Feb 2015 H1 M2 Apache-2.0 Yes Details →
3.11 22 Dec 2014 H1 M2 Apache-2.0 Yes Details →
3.11-beta3 18 Nov 2014 H1 M3 Apache-2.0 Yes Details →
3.11-beta2 20 Aug 2014 H1 M3 Apache-2.0 Yes Details →
3.10.1 18 Aug 2014 H1 M3 Apache-2.0 Yes Details →
3.11-beta1 04 Aug 2014 H1 M3 Apache-2.0 Yes Details →
3.10-FINAL 09 Feb 2014 H1 M5 Apache-2.0 Yes Details →
3.10-beta2 09 Sep 2013 H1 M5 Apache-2.0 Yes Details →
3.10-beta1 02 Jul 2013 H1 M5 Apache-2.0 Yes Details →
3.9 06 Dec 2012 H1 M6 Apache-2.0 Yes Details →
3.8 27 Mar 2012 H1 M6 Apache-2.0 Yes Details →
3.8-beta5 19 Dec 2011 H1 M6 Apache-2.0 Yes Details →
3.8-beta4 29 Aug 2011 H1 M6 Apache-2.0 Yes Details →
3.8-beta3 06 Jun 2011 H1 M6 Apache-2.0 Yes Details →
3.8-beta2 10 Apr 2011 H1 M6 Apache-2.0 Yes Details →
3.8-beta1 07 Mar 2011 H1 M6 Apache-2.0 Yes Details →
3.7 31 Oct 2010 H1 M6 Apache-2.0 Yes Details →
3.7-beta3 24 Sep 2010 H1 M6 Apache-2.0 Yes Details →
3.7-beta2 11 Aug 2010 H1 M6 Apache-2.0 Yes Details →
3.7-beta1 22 Jun 2010 H1 M6 Apache-2.0 Yes Details →
3.6 15 Dec 2009 H1 M6 Apache-2.0 Yes Details →
3.5-FINAL 28 Sep 2009 H1 M6 Apache-2.0 Yes Details →
3.5-beta6 22 Jun 2009 H1 M6 Apache-2.0 Yes Details →
3.5-beta5 20 Feb 2009 H1 M6 Apache-2.0 Yes Details →
3.5-beta4 02 Dec 2008 H1 M6 Apache-2.0 Yes Details →
3.2-FINAL 19 Oct 2008 H1 M6 Apache-2.0 Yes Details →
3.5-beta3 28 Sep 2008 H1 M6 Apache-2.0 Yes Details →
3.5-beta1 18 Jul 2008 H1 M6 Apache-2.0 Yes Details →
3.1-FINAL 30 Jun 2008 H1 M6 Apache-2.0 Yes Details →
3.1-beta2 27 May 2008 H1 M6 Apache-2.0 Yes Details →
3.1-beta1 29 Apr 2008 H1 M6 Apache-2.0 Yes Details →
3.0.2-FINAL 06 Feb 2008 H1 M6 Apache-2.0 Yes Details →
3.0.2-beta2 13 Jan 2008 H1 M6 Apache-2.0 Yes Details →
3.0.2-beta1 06 Dec 2007 H1 M6 Apache-2.0 Yes Details →
3.0.1-FINAL 06 Jul 2007 H1 M6 Apache-2.0 Yes Details →
3.0-FINAL 30 May 2007 H1 M6 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 6

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.poi:poi

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-12626: Denial of Service in Apache POI 7.5 high 3.17 14 Jan 2021
CVE-2019-12415: Apache POI - Improper Restriction of XML External Entity Reference 5.5 medium 4.1.1 24 May 2022
CVE-2017-5644: Apache POI - Improper Restriction of Recursive Entity References in DTDs 5.5 medium 3.15 13 May 2022
CVE-2014-3574: Improper Input Validation in Apache POI N/A medium 3.10.1 17 May 2022
CVE-2012-0213: Denial of Service in Apache POI N/A medium 3.10-beta1 04 May 2022

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.apache.poi:poi

Is org.apache.poi:poi safe to use?

Vulert records 7 vulnerabilities for org.apache.poi:poi in Maven: 0 critical, 1 high, 6 medium and 0 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.apache.poi:poi's Vulert package health score?

Vulert scores org.apache.poi:poi 93/100, which reads as healthy. 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.apache.poi:poi affected?

No. 6.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does org.apache.poi:poi have?

7 vulnerabilities are recorded for org.apache.poi:poi in the Maven ecosystem: 0 critical, 1 high, 6 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.poi:poi vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.poi:poi in the last 12 months, and the oldest entry in this database dates to 14 Jan 2021. 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.apache.poi:poi 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.apache.poi:poi for upcoming vulnerabilities?

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