PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-59932 PHPOffice CVE debrief

PhpSpreadsheet, a pure PHP library for reading and writing spreadsheet files, has a vulnerability in versions 4.0.0 through 5.8.0, 3.3.0 through 3.10.6, 2.2.0 through 2.4.6, 2.0.0 through 2.1.17, and all releases up to and including 1.30.5. The Gnumeric reader reads attacker-supplied .gnumeric files into memory and, when the file starts with gzip magic bytes, calls gzdecode() on the full compressed contents without enforcing a decompressed-size limit. This can lead to a denial of service (DoS) attack, causing the process to crash during Gnumeric::canRead() before the file is rejected or fully parsed. The vulnerability is reachable through normal file-type detection and Gnumeric loading paths, affecting applications that accept attacker-controlled spreadsheet uploads.

Vendor
PHPOffice
Product
PhpSpreadsheet
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-28
Original CVE updated
2026-10-23
Advisory published
2026-07-28
Advisory updated
2026-10-23

Who should care

Defenders responsible for applications that accept attacker-controlled spreadsheet uploads, specifically those using PhpSpreadsheet, should assess exposure and prioritize updates to fixed versions.

Why it matters

CVE-2026-59932 is a DoS vulnerability in PhpSpreadsheet's Gnumeric reader, affecting multiple versions. Defenders should prioritize updates to fixed versions and validate user-uploaded files to prevent potential attacks.

  • Denial of service (DoS) attacks through specially crafted .gnumeric files
  • Potential for memory exhaustion and process crashes
  • Need for validation and sanitization of user-uploaded files
  • Importance of updating to fixed PhpSpreadsheet versions

Technical summary

The Gnumeric reader in PhpSpreadsheet does not enforce a decompressed-size limit when reading attacker-supplied .gnumeric files, leading to a potential denial of service (DoS) attack. The vulnerability affects multiple versions of PhpSpreadsheet (4.0.0 through 5.8.0, 3.3.0 through 3.10.6, 2.2.0 through 2.4.6, 2.0.0 through 2.1.17, and all releases up to and including 1.30.5) and is reachable through normal file-type detection and Gnumeric loading paths. Defenders should prioritize updating PhpSpreadsheet to a fixed version and validate user-uploaded files to prevent potential attacks.

Defensive priority

Defenders should prioritize updating PhpSpreadsheet to a fixed version, specifically versions 5.8.1, 3.10.7, 2.4.7, 2.1.18, or 1.30.6, to prevent potential DoS attacks. They should also validate and sanitize user-uploaded files, implement memory limit checks, and monitor for suspicious activity.

Recommended defensive actions

  • Update PhpSpreadsheet to a fixed version (5.8.1, 3.10.7, 2.4.7, 2.1.18, or 1.30.6)
  • Validate and sanitize user-uploaded files
  • Implement memory limit checks
  • Monitor for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, affected versions, and fixed versions. GitHub commits and release tags offer additional context on the patches and affected code.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-59932 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-59932

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-59932 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-59932

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.