Vulnerability Database · Debian · libapache-poi-java · Version

libapache-poi-java 4.0.1-2

4.0.1-2 is affected by 6 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 0 Medium 2 Low 0 Unrated 4

Database updated 23/Oct/2026

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 Vulnerabilities affecting this version

libapache-poi-java 4.0.1-2 vulnerabilities

6 vulnerabilities cover libapache-poi-java 4.0.1-2. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Apache POI - XML External Entity (XXE) Processing 5.5 medium No fix published 23 Oct 2019
Apache POI - Arbitrary File Read Vulnerability (CVE-2016-5000) 5.5 medium No fix published 05 Aug 2016
Improper Input Validation in Apache POI - libapache-poi-java Vulnerability N/A unrated No fix published 09 Apr 2025
Improper Input Validation in Apache POI: libapache-poi-java Vulnerability N/A unrated No fix published 09 Apr 2025
Critical XXE Vulnerability in libapache-poi-java: Risk of Local File Exposure N/A unrated No fix published 23 Oct 2019
Apache POI XXE Vulnerability in libapache-poi-java: Remote File Access Risk N/A unrated No fix published 05 Aug 2016

Looking for another version, or everything Vulert holds for libapache-poi-java?

All versions → Full vulnerability list →

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 libapache-poi-java 4.0.1-2

Is libapache-poi-java 4.0.1-2 vulnerable?

Yes. 6 vulnerabilities in the Vulert database cover libapache-poi-java 4.0.1-2: 0 critical, 0 high, 2 medium and 0 low, plus 4 not yet rated. Each entry above names the fixed version to move to.

How do I monitor libapache-poi-java for upcoming vulnerabilities?

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