CVE-2026-108360

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.4 from GitHub Security Advisory (severity: MODERATE) published 2026-10-27. A secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-108264 (ENISA EUVD) · GHSA-2phh-27fw-q4gc (GitHub Security Advisories)Source: ENISA EUVD

6.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.4
EG Score
6.4MEDIUMhigh confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity64% × 45%
Impact severity (EG Severity): CVSS 6.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.4): severity, escalated by confirmed exploitation. This CVE's 6.4 is its impact severity (EG Severity), not escalated.

EG Severity
6.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 22, 2026

Last Modified

October 29, 2026

Advisory Details (10)

Auto-updated Oct 22, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

3.10.8

Patch available: PHPOffice/PhpSpreadsheet 3.10.8

https://github.com/PHPOffice/PhpSpreadsheet/releases/tag/3.10.8
GitHub release Patch Available

2.4.8

Patch available: PHPOffice/PhpSpreadsheet 2.4.8

https://github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.4.8
GitHub release Patch Available

2.1.19

Patch available: PHPOffice/PhpSpreadsheet 2.1.19

https://github.com/PHPOffice/PhpSpreadsheet/releases/tag/2.1.19
GitHub release Patch Available

1.30.7

Patch available: PHPOffice/PhpSpreadsheet 1.30.7

https://github.com/PHPOffice/PhpSpreadsheet/releases/tag/1.30.7
GitHub commit Patch Available

commit da13f40e8760 (PHPOffice/PhpSpreadsheet)

Patch available: PHPOffice/PhpSpreadsheet 1.30.7 (contains commit da13f40e8760)

https://github.com/PHPOffice/PhpSpreadsheet/commit/da13f40e8760d599b0e8a296017d4b028b20e86c
GitHub commit Patch Available

commit 9a0b48622ebf (PHPOffice/PhpSpreadsheet)

Patch available: PHPOffice/PhpSpreadsheet 2.4.8 (contains commit 9a0b48622ebf)

https://github.com/PHPOffice/PhpSpreadsheet/commit/9a0b48622ebfe93fa48cb9bc09ce57303bb07af9
GitHub commit Patch Available

commit 980b5c294493 (PHPOffice/PhpSpreadsheet)

Patch available: PHPOffice/PhpSpreadsheet 3.10.8 (contains commit 980b5c294493)

https://github.com/PHPOffice/PhpSpreadsheet/commit/980b5c294493856f1a25754f1e8a1d2185b93738
GitHub commit Patch Available

commit 94590951d76a (PHPOffice/PhpSpreadsheet)

Patch available: PHPOffice/PhpSpreadsheet 5.10.0 (contains commit 94590951d76a)

https://github.com/PHPOffice/PhpSpreadsheet/commit/94590951d76a250a5fc1ecf69a0b3f7439a9af49
GitHub commit Patch Available

commit 299993894dce (PHPOffice/PhpSpreadsheet)

Patch available: PHPOffice/PhpSpreadsheet 2.1.19 (contains commit 299993894dce)

https://github.com/PHPOffice/PhpSpreadsheet/commit/299993894dce37aa3b64aa23e9a3f4bb77ab0e66
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

SSRF whitelist bypass via unre-validated HTTP redirect in Drawing::setPath external image loading · Advisory · PHPOffice/PhpSpreadsheet · GitHub

https://github.com/PHPOffice/PhpSpreadsheet/security/advisories/GHSA-2phh-27fw-q4gc

Vendor Advisories for CVE-2026-108360(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerphpoffice/phpspreadsheet @ 5.10.0 (fixes >= 4.0.0, <= 5.9.0)—ghsa
composerphpoffice/phpspreadsheet @ 3.10.8 (fixes >= 3.3.0, <= 3.10.7)—ghsa
composerphpoffice/phpspreadsheet @ 2.4.8 (fixes >= 2.2.0, <= 2.4.7)—ghsa
composerphpoffice/phpspreadsheet @ 2.1.19 (fixes >= 2.0.0, <= 2.1.18)—ghsa
composerphpoffice/phpspreadsheet @ 1.30.7 (fixes <= 1.30.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
phpoffice/phpspreadsheet4.0.0 ... 5.9.0 (18 versions)
  • 4.0.0 up to 5.10.0: fixed in 5.10.0
  • 3.3.0 up to 3.10.8: fixed in 3.10.8
  • 2.2.0 up to 2.4.8: fixed in 2.4.8
  • 2.0.0 up to 2.1.19: fixed in 2.1.19
  • every version up to 1.30.7: fixed in 1.30.7
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-2phh-27fw-q4gc · GitHub severity MODERATE · GitHub CVSS 6.4
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-29 12:27 UTCEG score recompute
  8. 2026-10-29 11:59 UTCEG score recompute
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-25 14:54 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-23 19:47 UTCEG score recompute
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-22 18:27 UTCEG score recompute
  18. 2026-10-22 17:36 UTCEG score recomputeFirst assessed: 6.4 MEDIUM
  19. 2026-10-22 17:35 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-108360?
CVE-2026-108360 is a medium-severity vulnerability; its CVE record was published on October 22, 2026. 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…
When was the CVE record for CVE-2026-108360 published?
The CVE record for CVE-2026-108360 was published on October 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-108360 actively exploited?
CVE-2026-108360 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108360?
CVE-2026-108360 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108360?
A fix for CVE-2026-108360 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-108360 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-108360

Explore →

Is Your Infrastructure Affected by CVE-2026-108360?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs