CVE-2026-55220: Pimcore Hotspotimage unrestricted PHP object deserialization

CVE-2026-55220 · Severity: critical · CVSS 4 · Published 2026-08-28

Pimcore's Hotspotimage field (used for image annotation metadata in data objects) deserializes untrusted database columns without validating which classes can be instantiated. An attacker with database write access can inject malicious serialized PHP objects that execute arbitrary code through gadget chains when the object is loaded—for instance, during admin UI rendering or API calls. This affects multiple field types (Hotspotimage, ImageGallery, Block, Video) across all maintained versions.

Technologies: pimcore/pimcore (Packagist), Pimcore. Vendors: Packagist, Pimcore.

Quick answers

Is CVE-2026-55220 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-55220 being exploited in the wild.
How severe is CVE-2026-55220?
Critical severity, with a CVSS score of 4, published 28 August 2026.
Which products and versions are affected?
pimcore/pimcore (Packagist) ECOSYSTEM:introduced=2026.1.0,fixed=2026.1.6; Pimcore 2026.1.0 through 2026.1.5, 12.0.0 through 12.3.9 (all currently maintained releases).
Is there a fix for CVE-2026-55220?
Yes. pimcore/pimcore (Packagist): upgrade to 2026.1.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55220 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-55220?
Check whether you run pimcore/pimcore (Packagist) or Pimcore at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • pimcore/pimcore (Packagist): upgrade to 2026.1.6 or later
    composer require pimcore/pimcore:^2026.1.6

Technical details

The vulnerability is a PHP Object Injection (CWE-502) in the Hotspotimage field marshaller and its siblings (ImageGallery, Block, Video). The `getDataFromResource()` method deserializes the `*__hotspots` database column via `Serialize::unserialize()`, which defaults to unrestricted class instantiation (`allowed_classes=true`). When the JSON decode fallback fails (which it does for PHP-serialized bytes), the code paths directly to `unserialize()` without a class allowlist. An attacker who can write crafted serialized bytes to the column—via SQL injection, direct database access, or other persistence layer vulnerabilities—triggers arbitrary class instantiation and magic method execution on any object load (admin grid, frontend render, API, inheritance walks). The PoC demonstrates file write via `GuzzleHttp\Cookie\FileCookieJar` gadget from bundled `guzzlehttp/guzzle 7.11.0`. The fix is to flip `Serialize::unserialize()`'s default `$allowedClasses` parameter from `true` to `false`, or pass an explicit allowlist at each call site.

Affected products

  • pimcore pimcore 2026.1.0 through 2026.1.5, 12.0.0 through 12.3.9 (all currently maintained releases)

Identifiers

  • CVE-2026-55220
  • GHSA-w23p-wrp7-ch38

Timeline

  • 2026-07-30: disclosed
  • 2026-08-28: advisory
  • 2026-08-28: patched: Patched in 2026.1.6 and 12.3.10

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.