OSV-2026-177
Security exception in org.apache.poi.util.IOUtils.safelyAllocate
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=479908886
Crash type: Security exception
Crash state:
org.apache.poi.util.IOUtils.safelyAllocate
org.apache.poi.hssf.record.RecordInputStream.readRemainder
org.apache.poi.hssf.record.UnknownRecord.<init>
What each source reports
OSV No score
Security exception in org.apache.poi.util.IOUtils.safelyAllocate
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=479908886
Crash type: Security exception
Crash state:
org.apache.poi.util.IOUtils.safelyAllocate
org.apache.poi.hssf.record.RecordInputStream.readRemainder
org.apache.poi.hssf.record.UnknownRecord.<init>
- Record
OSV-2026-177- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
apache-poiOSS-Fuzz |
Listed versions, plus commit ranges REL_5_5_0REL_5_5_1 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2026-177 is a vulnerability with no CVSS score yet in apache-poi, published February 2, 2026. No source lists public exploit code. A source reports a fix.