pimcore/pimcore security advisory

CVE-2026-45162: Pimcore has Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction

CVE-2026-45162 is a high-severity PHP object injection vulnerability in the PHP package pimcore/pimcore (CVSS 8.0), published 17 July 2026. It is fixed in 2026.1.3; earlier versions are affected. Exploiting it needs an admin-level account.

high 8.0 published 2026-07-17 · updated 2026-07-22

Affected versions: <= 11.5.16
>= 12.0.0-RC1, <= 12.3.6
>= 2026.1.0, < 2026.1.3
Fixed in: 2026.1.3
Newest release: 2026.3.4
Severity: High · CVSS 8.0
Type: PHP object injection
CWE-502
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your pimcore/pimcore version affected?

Run composer show pimcore/pimcore in your project, then enter the version. We check it against this and every other known pimcore/pimcore advisory.

Who can exploit CVE-2026-45162

Access: A high-privilege account in the app, such as an admin.
Conditions: It only works under specific conditions the attacker does not fully control (CVSS rates the attack as high complexity).

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Your app is only exposed if it uses the affected part of pimcore/pimcore. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-45162 in pimcore/pimcore

Find the installed version: composer show pimcore/pimcore. If you never required it yourself, composer why pimcore/pimcore shows which package pulls it in.
Update it: composer update pimcore/pimcore --with-all-dependencies. You need 2026.1.3 or newer.
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "pimcore/pimcore": "^2026.1.3" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-45162.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for PHP object injection issues while the upgrade waits. None of it replaces the fix.

Never pass user-controlled data to unserialize() or to template rendering, and restrict who can edit templates or settings.
Put a web application firewall in front of the app and watch for new PHP files or admin users.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-45162 advisory

Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.7, multiple Pimcore locations call PHP's unserialize() on data from database columns and filesystem files without the allowed_classes restriction, including lib/Tool/Authentication.php, models/Site/Dao.php, models/DataObject/ClassDefinition/CustomLayout/Dao.php, models/Tool/TmpStore/Dao.php, models/Asset/WebDAV/Service.php, and admin-ui-classic-bundle/src/Helper/Dashboard.php, enabling object injection and remote code execution if an attacker can control the serialized data source. This issue is fixed in versions 11.5.17 (LTS) and 12.3.7.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-45162. Advisory title: “Pimcore has Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction”.

References

GitHub advisory GHSA-36fc-7wjg-mfvj github.com
Fix commit 4788bf3 github.com
Pull request #19119 github.com
Release v12.3.7 github.com

Other pimcore/pimcore advisories

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.