Unsafe Deserialization in pimcore/pimcore (CVE-2026-45162)
Summary
Vulnerability in pimcore/pimcore (CVE-2026-45162). Successful exploitation can lead to full system takeover. Exploitable via allowed_classes. Mitigation: upgrade to 2026.1.3 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45162 has been found in pimcore/pimcore.
Attackers can target a specific entry point like allowed_classes over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: upgrade pimcore/pimcore to 2026.1.3 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2026-45162" on the vendor's site.
CVE-2026-45162 (pimcore/pimcore) — CWE-502 / CVSS v3 8.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: allowed_classes / tmp_store / sites / custom_layouts
Patched: 2026.1.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in pimcore/pimcore. Attackers reach the vulnerable code path via allowed_classes.
Check the vendor advisory for the affected versions of pimcore/pimcore. Attack surface: allowed_classes / tmp_store / sites / custom_layouts.
Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.
Update to 2026.1.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pimcore/pimcore' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pimcore/pimcore' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pimcore/pimcoreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pimcore/pimcore to 2026.1.3ステージング環境で 2026.1.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com