Skip to content
Applications

CVE-2026-55220

9.3
Critical
EPSS 0.50%Patch availableSep 1, 2026

Pimcore PHP deserialization RCE via Hotspotimage __hotspots column

common questions

Is CVE-2026-55220 being exploited?

Not confirmed. CVE-2026-55220 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.

How severe is CVE-2026-55220?

CVE-2026-55220 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-55220?

Yes. A fix has been recorded for CVE-2026-55220. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-55220 affect?

CVE-2026-55220 affects Pimcore < 11.5.19, Pimcore < 12.3.10, Pimcore < 2026.1.6, Hotspotimage data field (related ImageGallery/Block/Video callers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-55220?

Upgrade to 11.5.19/12.3.10/2026.1.6; sanitize object-store serialized fields and restrict write access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Pimcore < 11.5.19Pimcore < 12.3.10Pimcore < 2026.1.6Hotspotimage data field (related ImageGallery/Block/Video callers)
impact

Attacker able to write crafted PHP serialized bytes to the __hotspots column can trigger deserialization, causing arbitrary file writes or remote code execution.

action required

Immediate action required

affected versions
pimcore pimcore
  • affected< 11.5.19
  • affected>= 12.0.0-RC1 and < 12.3.10
  • affected>= 2026.1.0 and < 2026.1.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free