CVE-2026-108358 json
PhpSpreadsheet: XmlScanner Bypass via ISO-2022 Escape Sequences Allows XXE and Denial of Service
published 2026-10-22 17 d ago modified 2026-10-27 13 d ago also EUVD-2026-108265 , GHSA-3x94-m842-937c
- cvss
- 8.8
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
PhpSpreadsheet is a pure PHP library for reading and writing spreadsheet files. Prior to 1.30.7, 2.1.19, 2.4.8, 3.10.8, and 5.10.0, XmlScanner::scan in src/PhpSpreadsheet/Reader/Security/XmlScanner.php uses a DOCTYPE detection pattern that accounts for NUL-byte interleaving but not ISO-2022 escape sequences in XLSX XML parts. The escape sequences prevent the scanner from matching the declaration, and XML charset normalization then removes the escape bytes before parsing, exposing a valid DOCTYPE and entity definitions. Processing an attacker-controlled XLSX can therefore cause entity-expansion denial of service on supported PHP versions and can permit local file access or SSRF on PHP before 8.0 or when LIBXML_NOENT is enabled. This issue is fixed in versions 1.30.7, 2.1.19, 2.4.8, 3.10.8, and 5.10.0.
Patch / fix
- packagist phpoffice/phpspreadsheet 1.30.7, 2.1.19, 2.4.8, 3.10.8, 5.10.0
- phpoffice phpspreadsheet 1.30.7, 2.1.19, 2.4.8, 3.10.8, 5.10.0
- phpspreadsheet_project phpspreadsheet 1.30.7, 2.1.19, 2.4.8, 3.10.8, 5.10.0
- github.com/PHPOffice/PhpSpreadsheet@2999938 commit
- github.com/PHPOffice/PhpSpreadsheet@89f455c commit
- github.com/PHPOffice/PhpSpreadsheet@980b5c2 commit
- github.com/PHPOffice/PhpSpreadsheet@9a0b486 commit
- github.com/PHPOffice/PhpSpreadsheet@da13f40 commit
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/1.30.7 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.1.19 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.4.8 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/3.10.8 release
- github.com/PHPOffice/PhpSpreadsheet/releases/tag/5.10.0 release
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 16 d ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.8 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:L/SI:N/SA:N |
| CNA | 4.0 | 8.8 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | phpoffice/phpspreadsheet | >=4.0.0, <5.10.0 >=3.3.0, <3.10.8 >=2.2.0, <2.4.8 >=2.0.0, <2.1.19 <1.30.7 |
5.10.0 3.10.8 2.4.8 2.1.19 1.30.7 |
Affected products
- PHPOffice PhpSpreadsheet
Classification
References
-
github.com
/PHPOffice/PhpSpreadsheet/commit/299993894dce37aa3b64aa23e9a3f4bb77ab0e66
web
-
github.com
/PHPOffice/PhpSpreadsheet/commit/89f455c133e1a7e2d4abfadc43ce29eb7450d781
web
-
github.com
/PHPOffice/PhpSpreadsheet/commit/980b5c294493856f1a25754f1e8a1d2185b93738
web
-
github.com
/PHPOffice/PhpSpreadsheet/commit/9a0b48622ebfe93fa48cb9bc09ce57303bb07af9
web
-
github.com
/PHPOffice/PhpSpreadsheet/commit/da13f40e8760d599b0e8a296017d4b028b20e86c
web
-
github.com
/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-3x94-m842-937c
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/1.30.7
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/2.1.19
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/2.4.8
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/3.10.8
web
-
github.com
/PHPOffice/PhpSpreadsheet/releases/tag/5.10.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-108358
advisory
-
github.com
/PHPOffice/PhpSpreadsheet
package
Sources
- CVE List CVE-2026-108358
- GitHub Advisory GHSA-3x94-m842-937c
- NVD CVE-2026-108358
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.