# CVE-2026-55220: Pimcore Hotspotimage getDataFromResource() unrestricted Serialize::unserialize over object-store column

> Attackers with write access to specific database columns can trigger unsafe deserialization in Pimcore, leading to arbitrary code execution or file writes.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-w23p-wrp7-ch38

## What is CVE-2026-55220?

CVE-2026-55220 is a critical unsafe deserialization vulnerability in pimcore, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-55220?

4 open source packages ship an affected version, including pimcore/pimcore.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/pimcore` | Packagist | All versions | 12.3.10 |
| `pimcore/pimcore` | Packagist | All versions | 12.3.10 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.6 |
| `pimcore/pimcore` | Packagist | From 2026.1.0 | 2026.1.6 |

## How do I fix CVE-2026-55220?

Upgrade pimcore/pimcore to a fixed version for your release line: 12.3.10 or 2026.1.6.

## Is CVE-2026-55220 being exploited?

There is no known exploitation of CVE-2026-55220 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55220 and fix it if it is affected.

What it is: CVE-2026-55220 is a critical unsafe deserialization vulnerability in pimcore, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55220 in the wild and no public exploit code.

Affected packages and fixed versions:
- pimcore/pimcore (Packagist): affected all versions; fixed in 12.3.10
- pimcore/pimcore (Packagist): affected all versions; fixed in 12.3.10
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.6
- pimcore/pimcore (Packagist): affected from 2026.1.0; fixed in 2026.1.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55220/ (Markdown: https://insights.sbomify.com/CVE-2026-55220/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55220
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55220
- OSV: https://osv.dev/vulnerability/CVE-2026-55220

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55220/
Summaries are generated and may contain mistakes; the official description above is the record.