Is org.apache.poi:poi 4.0 vulnerable?

Maven · 2 releases from 4.0.0 to 4.0.1 · latest org.apache.poi:poi is 6.0.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. org.apache.poi:poi 4.0.1, the last 4.0 release, is affected by 1 known security advisory (1 medium), including CVE-2019-12415. Upgrade to 4.1.1 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.poi:poi -DdepVersion=4.1.1 -DforceVersion=true

Is your project on an affected org.apache.poi:poi?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting org.apache.poi:poi 4.0.1

  • MediumCVE-2019-12415GHSA-9jwc-q6j3-8g9g24 May 2022

    Improper Restriction of XML External Entity Reference in Apache POI

    Affected
    <4.1.1
    Fixed in
    4.1.1

Every org.apache.poi:poi 4.0.x release

Affected: 4.0.0 to 4.0.1. Latest org.apache.poi:poi: 6.0.0.

VersionKnown advisories
org.apache.poi:poi 4.0.1CVE-2019-12415
org.apache.poi:poi 4.0.0CVE-2019-12415

Which of your client projects are still on org.apache.poi:poi 4.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.poi:poi version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.apache.poi:poi versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.