CVE Intelligence
Medium Access control

CVE-2026-108360 — PhpSpreadsheet: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading

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, Worksheet\Drawing::setPath validates only the initial external-image URL with setIsWhitelisted when setAllowExternalImages is enabled. The HTTP stream context permits PHP to follow a redirect without applying the callback to the redirected URL, so a permitted image host can redirect the server to an internal address and cause a blind GET request. The response body is not returned to the attacker because the reader validates the downloaded content as an image and removes the temporary file, but internal GET-driven endpoints, network reachability, and cloud metadata endpoints may be reached. This issue is fixed in versions 1.30.7, 2.1.19, 2.4.8, 3.10.8, and 5.10.0.

Published Oct 22, 2026 · Updated Oct 29, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (medium)+3
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.22%
ahead of 13% of scored CVEs · Oct 28, 2026
Affects
Phpoffice
Phpspreadsheet and 1 more
CVSS base
6.4
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Composer Phpoffice/phpspreadsheet: fixed in version 5.10.0 — github.com (GitHub Security Advisories)
  • Composer Phpoffice/phpspreadsheet: fixed in version 3.10.8 — github.com (GitHub Security Advisories)
  • Composer Phpoffice/phpspreadsheet: fixed in version 2.4.8 — github.com (GitHub Security Advisories)
  • Composer Phpoffice/phpspreadsheet: fixed in version 2.1.19 — github.com (GitHub Security Advisories)
  • Composer Phpoffice/phpspreadsheet: fixed in version 1.30.7 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Phpoffice Phpspreadsheet, Composer Phpoffice/phpspreadsheet).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Phpoffice Phpspreadsheet version < 1.30.7version >= 2.0.0, < 2.1.19version >= 2.2.0, < 2.4.8version >= 3.3.0, < 3.10.8version >= 4.0.0, < 5.10.0 Vulnerable CVE Program (cve.org) e CISA ADP
Composer Phpoffice/phpspreadsheet ≥ 4.0.0 and ≤ 5.9.0≥ 3.3.0 and ≤ 3.10.7≥ 2.2.0 and ≤ 2.4.7≥ 2.0.0 and ≤ 2.1.18≤ 1.30.6 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.4 CVSS 3.1 Medium 3.1 2.7 security-advisories@github.com via NIST National Vulnerability Database
6.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
6.4 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 28, 2026 · 6 reading(s) · max 0.22%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 29, 2026 · GitHub Security Advisories
  • Affected products added · composer/phpoffice/phpspreadsheet
    Oct 29, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Awaiting Analysis
    Oct 23, 2026 · NIST National Vulnerability Database
  • Affected products added · phpoffice/phpspreadsheet
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 22, 2026
  • CVSS changed · 6.4
    Oct 22, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 22, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 22, 2026 · Alertas do Telegram
  • CVE published
    Oct 22, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 22, 2026 – Oct 29, 2026
  • 1× Official description updated · Oct 22, 2026 – Oct 22, 2026

References

13 on the record

Elsewhere on this site

Phpoffice
every CVE for this vendor
Access control
same class
CWE-863
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-108357 PhpSpreadsheet: XmlScanner Bypass via Double-Encoded unentity() TOCTOU Allows XXE and Denial of Service 6d
  • CVE-2026-108358 PhpSpreadsheet: XmlScanner Bypass via ISO-2022 Escape Sequences Allows XXE and Denial of Service 6d
  • CVE-2026-108359 PhpSpreadsheet ODS Reader: Unbounded number-rows-repeated → CPU & Memory Exhaustion (DoS) 6d
  • CVE-2026-59932 PhpSpreadsheet: Gnumeric reader unbounded gzip expansion causes memory exhaustion Jul 28, 2026
  • CVE-2026-59933 PhpSpreadsheet: XLS/OLE sector-chain self-loop causes memory exhaustion Jul 28, 2026
  • CVE-2026-59931 PhpSpreadsheet: SSRF bypass via HTTP redirect in WEBSERVICE() domain whitelist Jul 28, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-108360 is "PhpSpreadsheet: SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading", rated Medium. It affects Phpspreadsheet (Phpoffice); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.4 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.