CVE-2026-55416

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% 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
8.8EG
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.8Exploit: None knownExposed: 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.19, 12.3.10, and 2026.1.6, an authenticated user with reports_config permission can place attacker-controlled SQL fragments in the sql, from, where, and groupby fields of a Custom Reports configuration processed by bundles/CustomReportsBundle/src/Tool/Adapter/Sql.php. The buildQueryString() method concatenates these values into a database query, while a blacklist omits dangerous constructs such as additional data-manipulation statements, comments, subqueries, and multiple statements. The getData() method also previously interpolated offset and limit values into a LIMIT clause without integer casting. Executing the configured report reaches fetchAllAssociative() with the constructed query and can disclose, modify, or delete arbitrary database data. This issue is fixed in versions 11.5.19, 12.3.10, and 2026.1.6.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 16, 2026

Advisory Details (5)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
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_release Patch Available

12.3.10

Patch available: pimcore/pimcore v12.3.10

https://github.com/pimcore/pimcore/releases/tag/v12.3.10
github_commit Patch Available

commit 1999fee27ed0 (pimcore/pimcore)

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

https://github.com/pimcore/pimcore/commit/1999fee27ed0d027ad5b8195ecf6e27243729530
github_pr Patch Available

[Security]: Improve sql concatenation in Custom Reports

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

https://github.com/pimcore/pimcore/pull/19175
github Patch Available🟡 PoC Available

SQL Injection in Mautic Custom Reports Bundle (Sql.php:84-135) Due to Direct Concatenation of User-Controlled Configuration Fields Without Parameterization; Trivially Bypassable Blacklist Allows Full Database Read/Write/Delete · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-23rh-xw42-fq82

Vendor Advisories for CVE-2026-55416(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.5 (6 versions)2026.1.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 21× 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-09-25 00:57 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-24 01:04 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 01:12 UTCEG score recompute
  6. 2026-09-22 01:20 UTCEG score recompute
  7. 2026-09-21 01:24 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-20 01:20 UTCEG score recompute
  10. 2026-09-19 01:28 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 01:34 UTCEG score recompute
  13. 2026-09-17 19:31 UTCEPSS rescore
  14. 2026-09-17 01:42 UTCEG score recompute
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 08:51 UTCEG score recompute
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-14 20:27 UTCEG score recompute
  19. 2026-09-14 20:15 UTCEG score recompute
  20. 2026-09-14 17:28 UTCEG score recompute
  21. 2026-09-10 20:24 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55416?
CVE-2026-55416 is a high vulnerability published on September 10, 2026. Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.19, 12.3.10, and 2026.1.6, an authenticated user with reports_config permission can place attacker-controlled SQL fragments in the sql, from, where, and groupby fields of a Custom Reports configuration processed by…
When was CVE-2026-55416 disclosed?
CVE-2026-55416 was first published in the National Vulnerability Database on September 10, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55416 actively exploited?
CVE-2026-55416 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 51.1% of all scored CVEs.
What is the CVSS score of CVE-2026-55416?
CVE-2026-55416 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-55416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55416, 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-55416

Explore →

Is Your Infrastructure Affected by CVE-2026-55416?

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

Book a Demo →Browse All CVEs