CVE-2026-55634

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.19, 12.3.10, and 2026.1.6, the class-definition import endpoint /pimcore-studio/api/class/definition/configuration-view/detail/{id}/import accepts a DataObject field name that is emitted without an identifier allowlist by lib/DataObject/ClassBuilder/FieldDefinitionPropertiesBuilder.php into generated PHP properties and by models/DataObject/ClassDefinition/Helper/Dao.php into ALTER TABLE identifiers. An authenticated user with the objects permission can inject PHP syntax into the generated DataObject class, causing attacker-controlled code in generated var/classes/DataObject/.php files to run when an object of that class is instantiated, and can also inject SQL identifier content into schema-changing statements. The central models/DataObject/ClassDefinition/Data.php::setName() validation did not reject semicolons, braces, backticks, spaces, or other non-identifier characters. This issue is fixed in versions 11.5.19, 12.3.10, and 2026.1.6.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

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 (value × EchelonGraph’s weight)
Severity99% × 45%
The EG Score, 9.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
49th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

Pimcore Platform - SQL Injection in DataObject composite index handling during class definition import/save · CVE-2026-5394 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-r2f4-ff2p-xc64
GitHub advisoryMentions a patch (unverified)

Remote Code Execution via DataObject Class-Definition Field Name in Pimcore 12.x · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-9x44-4gxf-8c25
GitHub release Patch Available

2026.1.6

Patch available: pimcore/pimcore v2026.1.6

https://github.com/pimcore/pimcore/releases/tag/v2026.1.6
GitHub pull request Patch Available

[Security] Harden field name validation

Patch available: pimcore/pimcore v12.3.10 (PR #19183 merged 2026-06-12)

https://github.com/pimcore/pimcore/pull/19183
GitHub commit Patch Available

commit a4f8c3cfee58 (pimcore/pimcore)

Patch available: pimcore/pimcore v12.3.10 (contains commit a4f8c3cfee58)

https://github.com/pimcore/pimcore/commit/a4f8c3cfee58b7d5fe4873d67782eff58dae9b9d

Vendor Advisories for CVE-2026-55634(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 rangeFix by version rangeDependents
pimcore/pimcorev2026.1.0 ... v2026.1.5 (6 versions)
  • every version up to 12.3.10: fixed in 12.3.10
  • 2026.1.0 up to 2026.1.6: fixed in 2026.1.6
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 58× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  2. 2026-10-13 14:09 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-10-12 15:32 UTCEG score recompute
  5. 2026-10-11 19:38 UTCEG score recompute
  6. 2026-10-11 16:54 UTCEG score recompute
  7. 2026-10-11 14:16 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  10. 2026-10-10 00:49 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  12. 2026-10-09 02:37 UTCEG score recompute
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  14. 2026-10-08 00:50 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-10-06 15:55 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-10-05 20:41 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  20. 2026-10-04 23:28 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-10-03 17:29 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-10-02 21:45 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 49th percentile
Show 64 more
  1. 2026-10-02 00:36 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  3. 2026-09-30 19:48 UTCEG score recompute
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  5. 2026-09-30 03:49 UTCEG score recompute
  6. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  7. 2026-09-29 01:02 UTCEG score recompute
  8. 2026-09-28 15:19 UTCEG score recompute
  9. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  10. 2026-09-27 15:51 UTCEG score recompute
  11. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  12. 2026-09-26 19:26 UTCEG score recompute
  13. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  14. 2026-09-26 08:03 UTCEG score recompute
  15. 2026-09-24 18:42 UTCEG score recompute
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  17. 2026-09-23 18:05 UTCEG score recompute
  18. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  19. 2026-09-22 14:56 UTCEG score recompute
  20. 2026-09-21 23:25 UTCEG score recompute
  21. 2026-09-20 20:18 UTCEG score recompute
  22. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  23. 2026-09-19 16:48 UTCEG score recompute
  24. 2026-09-18 21:28 UTCEG score recompute
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  26. 2026-09-17 20:50 UTCEG score recompute
  27. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  28. 2026-09-16 18:58 UTCEG score recompute
  29. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  30. 2026-09-16 09:10 UTCEG score recompute
  31. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  32. 2026-09-15 05:36 UTCEG score recompute
  33. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  34. 2026-09-13 18:06 UTCEG score recompute
  35. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  36. 2026-09-12 18:53 UTCEG score recompute
  37. 2026-09-11 15:45 UTCEG score recompute
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  39. 2026-09-11 11:53 UTCEG score recompute
  40. 2026-09-10 12:39 UTCEG score recompute
  41. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  42. 2026-09-09 00:26 UTCEG score recompute
  43. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  44. 2026-09-07 18:53 UTCEG score recompute
  45. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  46. 2026-09-06 14:16 UTCEG score recompute
  47. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  48. 2026-09-05 18:55 UTCEG score recompute
  49. 2026-09-04 15:16 UTCEG score recompute
  50. 2026-09-04 07:30 UTCEG score recompute
  51. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  52. 2026-09-02 15:35 UTCEG score recompute
  53. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  54. 2026-09-01 16:19 UTCEG score recompute
  55. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  56. 2026-09-01 08:33 UTCEG score recompute
  57. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  58. 2026-08-30 21:15 UTCEG score recompute
  59. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  60. 2026-08-30 01:54 UTCEG score recompute
  61. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  62. 2026-08-28 20:24 UTCEG score recompute
  63. 2026-08-28 19:38 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  64. 2026-08-28 19:36 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55634?
CVE-2026-55634 is a critical-severity vulnerability; its CVE record was published on August 28, 2026. Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.19, 12.3.10, and 2026.1.6, the class-definition import endpoint /pimcore-studio/api/class/definition/configuration-view/detail/{id}/import accepts a DataObject field name that is emitted without an identifier allowlist…
When was the CVE record for CVE-2026-55634 published?
The CVE record for CVE-2026-55634 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55634 actively exploited?
CVE-2026-55634 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55634?
CVE-2026-55634 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55634?
A fix for CVE-2026-55634 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55634 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55634?

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

Book a Demo →Browse All CVEs