CVE-2026-45162 is a high-severity (CVSS 8) Deserialization of Untrusted Data vulnerability in pimcore/pimcore. A fix is available for pimcore/pimcore — see the affected versions and patch details below.
Pimcore: Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-45162.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-45162 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
pimcore/pimcore🐘pimcore/pimcore🐘pimcore/pimcoreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
GitHub Security Advisory Draft — GM-374
Summary
Multiple locations in Pimcore v11 call PHP's unserialize() on data from database columns and filesystem files without the allowed_classes restriction, enabling object injection if an attacker can control the serialized data source.
Severity
CVSS 3.1: 8.0 (High) — AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Affected Component
- Package:
pimcore/pimcoreandpimcore/admin-ui-classic-bundle - Files:
lib/Tool/Authentication.php(line 82) — session token deserializationmodels/Site/Dao.php(line 68) — site domains from databasemodels/DataObject/ClassDefinition/CustomLayout/Dao.php(line 69) — layout definitions from databasemodels/Tool/TmpStore/Dao.php(line 64) — temporary store data from databasemodels/Asset/WebDAV/Service.php(line 36) — delete log from filesystemadmin-ui-classic-bundle/src/Helper/Dashboard.php(line 64) — dashboard config from filesystem
Description
Six locations in Pimcore core call unserialize() directly (bypassing Tool\Serialize) on data sourced from database columns or filesystem files without passing the allowed_classes parameter. This means any class available in the autoloader will be instantiated during deserialization.
If an attacker can write to the data source (e.g., via SQL injection targeting the tmp_store, sites, or custom_layouts tables, or via a file write vulnerability targeting the WebDAV delete log), they can inject serialized PHP gadget chains that execute arbitrary code when the data is deserialized.
This is related to but distinct from the Tool\Serialize::unserialize() issue — these calls bypass the wrapper entirely.
Impact
PHP object injection leading to Remote Code Execution when chained with a data source write vulnerability. Pimcore's dependency tree (Guzzle, Symfony, Monolog, Doctrine) provides numerous known gadget chains.
Proof of Concept
- Identify a writable data source (e.g.,
tmp_storetable via SQL injection, orwebdav-delete.datvia file write) - Write a serialized PHP gadget chain (e.g., Monolog
BufferHandlerchain from phpggc) - Trigger the deserialization (e.g., access a page that reads TmpStore, or trigger a WebDAV operation)
- The gadget chain executes with web server privileges
Suggested Fix
Add allowed_classes parameter to all unserialize() calls. Where no objects are needed, use ['allowed_classes' => false]. Consider migrating to JSON serialization for data that doesn't require object preservation.
// Example fix for Site/Dao.php:
$siteDomains = unserialize($site['domains'], ['allowed_classes' => false]);
// Example fix for TmpStore/Dao.php:
$item['data'] = unserialize($item['data'], ['allowed_classes' => false]);
References
- CWE-502: Deserialization of Untrusted Data
- OWASP Deserialization Cheat Sheet
- phpggc: PHP Generic Gadget Chains
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | pimcore/pimcore | ≥ 12.0.0-RC1&&< 12.3.7 | 12.3.7composer require pimcore/pimcore:^12.3.7 |
| 🐘Packagist | pimcore/pimcore | all versions | 11.5.17composer require pimcore/pimcore:^11.5.17 |
| 🐘Packagist | pimcore/pimcore | ≥ 2026.1.0&&< 2026.1.3 | 2026.1.3composer require pimcore/pimcore:^2026.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pimcore/pimcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/pimcore to 12.3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-45162 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is CVE-2026-45162 in your dependencies?
Find it across Packagist, including transitive dependencies.