CVE-2026-45162: Pimcore PHP object injection in multiple components

CVE-2026-45162 · Severity: high · CVSS 8 · Published 2026-07-17

Pimcore is an open-source platform used by businesses to manage digital data and customer experiences. A security vulnerability exists where the system improperly processes certain data stored in its database or files. If an attacker manages to modify this stored data, they could potentially take full control of the server, leading to data theft or service disruption.

Technologies: pimcore/pimcore (Packagist), Pimcore Admin UI Classic Bundle, Pimcore. Vendors: Packagist, Pimcore.

Quick answers

Is CVE-2026-45162 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45162 being exploited in the wild.
How severe is CVE-2026-45162?
High severity, with a CVSS score of 8, published 17 July 2026.
Which products and versions are affected?
pimcore/pimcore (Packagist) <= 12.3.6, ECOSYSTEM:introduced=12.0.0-RC1,fixed=12.3.7; Pimcore < 11.5.17, >= 12.0.0, < 12.3.7, <= 12.3.6.
Is there a fix for CVE-2026-45162?
Yes. pimcore/pimcore (Packagist): upgrade to 12.3.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45162 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-45162?
Check whether you run pimcore/pimcore (Packagist), Pimcore Admin UI Classic Bundle 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 12.3.7 or later
    composer require pimcore/pimcore:^12.3.7

Technical details

A PHP object injection vulnerability exists in multiple Pimcore components, including the Authentication tool, Site DAO, and WebDAV service. The root cause is the use of the native PHP unserialize() function on data retrieved from database columns and the filesystem without specifying the 'allowed_classes' restriction. While an attacker typically needs a secondary vulnerability (like SQL injection or file write) to control the serialized data source, successful exploitation allows them to leverage existing gadget chains (e.g., Guzzle, Monolog) to achieve remote code execution. The issue is fixed in versions 11.5.17 (LTS) and 12.3.7 by hardening the unserializer and refining allowed classes.

Affected products

  • Pimcore Pimcore < 11.5.17, >= 12.0.0, < 12.3.7

Identifiers

  • CVE-2026-45162
  • GHSA-36fc-7wjg-mfvj

Timeline

  • 2026-05-08: patched: Fix merged into version 12.3 branch
  • 2026-05-19: advisory: Release 12.3.7 published
  • 2026-05-26: disclosed: GitHub Security Advisory published
  • 2026-07-17: disclosed: CVE published to NVD

References

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