Answer in brief
CVE-2026-55220 records a Critical severity (CVSS 0.0) vulnerability in Pimcore Hotspotimage getDataFromResource() unrestricted Serialize::unserialize over object-store column. The current sources do not mark it as known exploited. The current feed maps pimcore/pimcore (composer), pimcore/pimcore (composer), pimcore/pimcore (generic), pimcore/pimcore (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps pimcore/pimcore (composer), pimcore/pimcore (composer), pimcore/pimcore (generic), pimcore/pimcore (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| pimcore/pimcorecomposer | <=12.3.9 | 12.3.10 |
| pimcore/pimcorecomposer | >=2026.1.0,<=2026.1.5 | 2026.1.6 |
| pimcore/pimcoregeneric | < 11.5.19 || >= 12.0.0-RC1, < 12.3.10 || >= 2026.1.0, < 2026.1.6 | Not reported |
| pimcore/pimcorepackagist | >=0 <12.3.10 | 12.3.10 |
| pimcore/pimcorepackagist | >=2026.1.0 <2026.1.6 | 2026.1.6 |
Published upstream
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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 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.
Quoted source text, attributed separately from HOL analysis.