CVE-2026-45162

HIGHPre-NVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.0
EG Score
8.0(medium)
EG Risk
52(Track*)
EG Risk 52/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity80% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 22, 2026

Advisory Details (4)

Auto-updated Jul 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Unsafe PHP Deserialization in Multiple Locations Without allowed_classes Restriction · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-36fc-7wjg-mfvj
github_release Patch Available

12.3.7

Patch available: pimcore/pimcore v12.3.7

https://github.com/pimcore/pimcore/releases/tag/v12.3.7
github_pr Patch Available

[Security]: Harden unserializer and refine allowed classes

Patch available: pimcore/pimcore v12.3.7 (PR #19119 merged 2026-05-08)

https://github.com/pimcore/pimcore/pull/19119
github_commit Patch Available

commit 4788bf3a3a7f (pimcore/pimcore)

Patch available: pimcore/pimcore v12.3.7 (contains commit 4788bf3a3a7f)

https://github.com/pimcore/pimcore/commit/4788bf3a3a7f2f760a8fe61e522565941e154e1e

Vendor Advisories for CVE-2026-45162(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
pimcore/pimcorev2026.1.0, v2026.1.1, v2026.1.22026.1.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 10:09 UTCEG score recompute
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:17 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:16 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:24 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-06-14 23:18 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-05-27 17:35 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-45162?
CVE-2026-45162 is a high vulnerability published on May 27, 2026. 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,…
When was CVE-2026-45162 disclosed?
CVE-2026-45162 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45162 actively exploited?
CVE-2026-45162 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.0% of all scored CVEs.
What is the CVSS score of CVE-2026-45162?
CVE-2026-45162 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-45162?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45162, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45162

Explore →

Is Your Infrastructure Affected by CVE-2026-45162?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs