CVE-2026-55220

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.19, 12.3.10, and 2026.1.6, Pimcore\Model\DataObject\ClassDefinition\Data\Hotspotimage::getDataFromResource() in models/DataObject/ClassDefinition/Data/Hotspotimage.php passes the field __hotspots object-store column to Pimcore\Tool\Serialize::unserialize() without an allowed-classes restriction after JSON decoding fails. An attacker with a separate capability to write crafted PHP serialized bytes into that column can instantiate available classes and trigger magic methods when an affected DataObject is loaded, which can produce arbitrary file writes or code execution through bundled gadget chains. The related ImageGallery, Block, and Video callers use the same fallback pattern, but the identified June fix changes the Hotspotimage caller only. This issue is fixed for Hotspotimage in versions 11.5.19, 12.3.10, and 2026.1.6.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
57(Track)
EG Risk 57/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
42%
KEV
Not listed

Published

August 28, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Pimcore Hotspotimage getDataFromResource() unrestricted Serialize::unserialize over object-store column (PHP Object Injection, CWE-502) · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-w23p-wrp7-ch38
github_release Patch Available

2026.1.6

Patch available: pimcore/pimcore v2026.1.6

https://github.com/pimcore/pimcore/releases/tag/v2026.1.6
github_release Patch Available

12.3.10

Patch available: pimcore/pimcore v12.3.10

https://github.com/pimcore/pimcore/releases/tag/v12.3.10
github_pr Patch Available

[Security]: Improve unserialize security in Hotspot Image

Patch available: pimcore/pimcore v12.3.10 (PR #19181 merged 2026-06-11)

https://github.com/pimcore/pimcore/pull/19181
github_commit Patch Available

commit b184c01bf11e (pimcore/pimcore)

Patch available: pimcore/pimcore v12.3.10 (contains commit b184c01bf11e)

https://github.com/pimcore/pimcore/commit/b184c01bf11e213e601d965b4e96c8bb7248e980

Vendor Advisories for CVE-2026-55220(1)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
pimcore/pimcore10.0.8 ... v6.9.6 (325 versions)12.3.10—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-20 21:41 UTCEG score recompute
  2. 2026-09-20 20:16 UTCEPSS rescore
  3. 2026-09-19 18:06 UTCEG score recompute
  4. 2026-09-18 21:28 UTCEG score recompute
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 20:50 UTCEG score recompute
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-16 15:38 UTCEG score recompute
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 07:44 UTCEG score recompute
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 04:03 UTCEG score recompute
  13. 2026-09-15 03:11 UTCEPSS rescore
  14. 2026-09-13 20:36 UTCEG score recompute
  15. 2026-09-13 16:47 UTCEPSS rescore
  16. 2026-09-12 17:05 UTCEG score recompute
  17. 2026-09-11 17:28 UTCEG score recompute
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-11 12:54 UTCEG score recompute
  20. 2026-09-10 12:59 UTCEG score recompute
  21. 2026-09-10 09:35 UTCEPSS rescore
  22. 2026-09-09 00:26 UTCEG score recompute
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-07 19:14 UTCEG score recompute
  25. 2026-09-07 16:01 UTCEPSS rescore
Show 21 more
  1. 2026-09-06 15:28 UTCEG score recompute
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-05 15:53 UTCEG score recompute
  4. 2026-09-04 16:05 UTCEG score recompute
  5. 2026-09-04 08:11 UTCEG score recompute
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 15:35 UTCEG score recompute
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 15:31 UTCEG score recompute
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 07:37 UTCEG score recompute
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-31 19:31 UTCEG score recompute
  14. 2026-08-31 18:57 UTCEG score recompute
  15. 2026-08-30 19:49 UTCEG score recompute
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 04:07 UTCEG score recompute
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 20:24 UTCEG score recompute
  20. 2026-08-28 19:38 UTCEG score recompute
  21. 2026-08-28 19:36 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55220?
CVE-2026-55220 is a critical vulnerability published on August 28, 2026. Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.19, 12.3.10, and 2026.1.6, Pimcore\Model\DataObject\ClassDefinition\Data\Hotspotimage::getDataFromResource() in models/DataObject/ClassDefinition/Data/Hotspotimage.php passes the field hotspots object-store column to…
When was CVE-2026-55220 disclosed?
CVE-2026-55220 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55220 actively exploited?
CVE-2026-55220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 58.3% of all scored CVEs.
What is the CVSS score of CVE-2026-55220?
CVE-2026-55220 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-55220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55220, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55220?

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

Start Free Scan →Browse All CVEs