Is org.apache.poi:poi-ooxml 4.1 vulnerable?
Maven · 3 releases from 4.1.0 to 4.1.2 · latest org.apache.poi:poi-ooxml is 6.0.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. org.apache.poi:poi-ooxml 4.1.2, the last 4.1 release, is affected by 1 known security advisory (1 medium), including CVE-2025-31672. Upgrade to 5.4.0 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.apache.poi:poi-ooxml -DdepVersion=5.4.0 -DforceVersion=trueIs your project on an affected org.apache.poi:poi-ooxml?
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-ooxml 4.1.2
Apache POI OOXML Vulnerable to Improper Input Validation in OOXML File Parsing
- Affected
- <5.4.0
- Fixed in
- 5.4.0
Every org.apache.poi:poi-ooxml 4.1.x release
Affected: 4.1.0 to 4.1.2. Latest org.apache.poi:poi-ooxml: 6.0.0.
| Version | Known advisories |
|---|---|
| org.apache.poi:poi-ooxml 4.1.2 | CVE-2025-31672 |
| org.apache.poi:poi-ooxml 4.1.1 | CVE-2025-31672 |
| org.apache.poi:poi-ooxml 4.1.0 | CVE-2025-31672 |
Which of your client projects are still on org.apache.poi:poi-ooxml 4.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.poi:poi-ooxml version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.poi:poi-ooxml versions
- org.apache.poi:poi-ooxml 5.2
- org.apache.poi:poi-ooxml 5.1
- org.apache.poi:poi-ooxml 5.0
- org.apache.poi:poi-ooxml 4.0
- org.apache.poi:poi-ooxml 3.17
- org.apache.poi:poi-ooxml 3.16
- org.apache.poi:poi-ooxml 6.0
- org.apache.poi:poi-ooxml 5.5
- org.apache.poi:poi-ooxml 5.4
- org.apache.poi:poi-ooxml 5.3
- All org.apache.poi:poi-ooxml advisories
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.