CVE-2026-45162: Pimcore/pimcore Pimcore Has Unsafe PHP Deserialization Vulnerability
HIGHCVE-2026-45162 is a HIGH (CVSS 8.0) pimcore has unsafe php deserialization vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Pimcore/pimcore libraries in the Packagist ecosystem. The issue involves pimcore has unsafe php deserialization in multiple locations without allowed_classes restriction. Remediation is available by upgrading affected packages to version 2026.1.3, 12.3.7, 11.5.17.
CVE-2026-45162 at a Glance
Security Impact
CVSS: 8.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-45162
To remediate this vulnerability, upgrade all affected Pimcore/pimcore dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade pimcore/pimcore to 2026.1.3
Upgrade pimcore/pimcore to 12.3.7
Upgrade pimcore/pimcore to 11.5.17
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for pimcore/pimcore
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-45162, inspect your project dependencies for Pimcore/pimcore:
inspect dependencies for pimcore/pimcore
Analyze the terminal output to locate any version of Pimcore/pimcore in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.1.3), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Pimcore/pimcore, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-45162 Affected Pimcore/pimcore Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
pimcore/pimcore
|
Packagist |
≥ 2026.1.0
< 2026.1.3
|
2026.1.3
|
|
pimcore/pimcore
|
Packagist |
≥ 12.0.0-RC1
< 12.3.7
|
12.3.7
|
|
pimcore/pimcore
|
Packagist |
< 11.5.17
|
11.5.17
|
References
Frequently Asked Questions
What is CVE-2026-45162?
Which Pimcore/pimcore versions are affected?
What version fixes CVE-2026-45162?
Is pimcore/pimcore affected?
What is the CVSS score of CVE-2026-45162?
What CWE is associated with CVE-2026-45162?
How can I check Packagist dependencies for CVE-2026-45162?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-36fc-7wjg-mfvj",
"modified" : "2026-07-10T19:07:27Z",
"published" : "2026-05-27T16:57:04Z",
"aliases" : [ "CVE-2026-45162" ],
"summary" : "Pimcore has Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction",
"details" : "# GitHub Security Advisory Draft — GM-374\n\n## Summary\nMultiple 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.\n\n## Severity\nCVSS 3.1: 8.0 (High) — AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H\n\n## Affected Component\n- **Package:** `pimcore/pimcore` and `pimcore/admin-ui-classic-bundle`\n- **Files:**\n - `lib/Tool/Authentication.php` (line 82) — session token deserialization\n - `models/Site/Dao.php` (line 68) — site domains from database\n - `models/DataObject/ClassDefinition/CustomLayout/Dao.php` (line 69) — layout definitions from database\n - `models/Tool/TmpStore/Dao.php` (line 64) — temporary store data from database\n - `models/Asset/WebDAV/Service.php` (line 36) — delete log from filesystem\n - `admin-ui-classic-bundle/src/Helper/Dashboard.php` (line 64) — dashboard config from filesystem\n\n## Description\nSix 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.\n\nIf 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.\n\nThis is related to but distinct from the `Tool\\Serialize::unserialize()` issue — these calls bypass the wrapper entirely.\n\n## Impact\nPHP 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.\n\n## Proof of Concept\n1. Identify a writable data source (e.g., `tmp_store` table via SQL injection, or `webdav-delete.dat` via file write)\n2. Write a serialized PHP gadget chain (e.g., Monolog `BufferHandler` chain from phpggc)\n3. Trigger the deserialization (e.g., access a page that reads TmpStore, or trigger a WebDAV operation)\n4. The gadget chain executes with web server privileges\n\n## Suggested Fix\nAdd `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.\n\n```php\n// Example fix for Site/Dao.php:\n$siteDomains = unserialize($site['domains'], ['allowed_classes' => false]);\n\n// Example fix for TmpStore/Dao.php:\n$item['data'] = unserialize($item['data'], ['allowed_classes' => false]);\n```\n\n## References\n- CWE-502: Deserialization of Untrusted Data\n- OWASP Deserialization Cheat Sheet\n- phpggc: PHP Generic Gadget Chains",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "pimcore/pimcore"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "12.0.0-RC1"
}, {
"fixed" : "12.3.7"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 12.3.6"
}
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "pimcore/pimcore"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "11.5.17"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 11.5.16"
}
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "pimcore/pimcore"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2026.1.0"
}, {
"fixed" : "2026.1.3"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/pimcore/pimcore/security/advisories/GHSA-36fc-7wjg-mfvj"
}, {
"type" : "WEB",
"url" : "https://github.com/pimcore/pimcore/pull/19119"
}, {
"type" : "WEB",
"url" : "https://github.com/pimcore/pimcore/commit/4788bf3a3a7f2f760a8fe61e522565941e154e1e"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/pimcore/pimcore"
}, {
"type" : "WEB",
"url" : "https://github.com/pimcore/pimcore/releases/tag/v12.3.7"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-27T16:57:04Z",
"nvd_published_at" : null
}
}