CVE-2026-44739

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% 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
Trending — 3 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: 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.6, the columnConfigAction endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php passes malicious SQL configuration through CustomReportController:columnConfigAction, SqlAdapter::getColumns, SqlAdapter::buildQueryString, and Db::fetchAssociative(), allowing an attacker with the reports_config permission to use arbitrary SELECT queries, UNION statements, dangerous database functions, and error-based SQL injection to exfiltrate or manipulate database data. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
55(Track*)
EG Risk 55/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
Severity87% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
33%
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_pr, github_commit, github_release, github.
github_release Patch Available

12.3.6

Patch available: pimcore/pimcore v12.3.6

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

commit 3fd7733464f4 (pimcore/pimcore)

Patch available: pimcore/pimcore v12.3.6 (contains commit 3fd7733464f4)

https://github.com/pimcore/pimcore/commit/3fd7733464f464e58ffa49ed91550c1a3f9535f2
github_pr Patch Available

[Security]: Enhance SQL security in Custom Report

Patch available: pimcore/pimcore v12.3.6 (PR #19098 merged 2026-04-29)

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

SQL Injection in Custom Reports Column Configuration · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-3234-gxc3-pq6f

Vendor Advisories for CVE-2026-44739(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/pimcorev12.0.0 ... v12.3.5 (25 versions)12.3.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 29× 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-16 05:15 UTCEPSS rescore
  2. 2026-09-14 09:34 UTCEG score recompute
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-12 15:01 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:37 UTCEPSS rescore
  7. 2026-09-11 01:23 UTCOSV refresh
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 15:53 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 21:13 UTCEG score recompute
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 54 more
  1. 2026-08-20 17:55 UTCEG score recompute
  2. 2026-08-19 17:04 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 16:29 UTCEG score recompute
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 03:00 UTCEG score recompute
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 02:05 UTCEG score recompute
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 01:39 UTCEG score recompute
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 14:07 UTCEG score recompute
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-12 01:52 UTCEG score recompute
  16. 2026-08-11 00:18 UTCEG score recompute
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-09 23:26 UTCEG score recompute
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-08 22:59 UTCEG score recompute
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 21:53 UTCEG score recompute
  23. 2026-08-06 21:26 UTCEG score recompute
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-05 21:00 UTCEG score recompute
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:38 UTCEPSS rescore
  29. 2026-08-02 04:23 UTCEG score recompute
  30. 2026-08-02 02:27 UTCEPSS rescore
  31. 2026-08-01 16:08 UTCEG score recompute
  32. 2026-08-01 04:16 UTCEPSS rescore
  33. 2026-07-31 08:20 UTCEG score recompute
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-29 16:22 UTCEG score recompute
  37. 2026-07-28 15:36 UTCEPSS rescore
  38. 2026-07-27 14:13 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-25 14:18 UTCEPSS rescore
  42. 2026-07-24 14:17 UTCEPSS rescore
  43. 2026-07-23 14:18 UTCEPSS rescore
  44. 2026-07-23 03:15 UTCEG score recompute
  45. 2026-07-22 14:08 UTCEPSS rescore
  46. 2026-07-21 15:24 UTCEPSS rescore
  47. 2026-07-20 17:08 UTCEPSS rescore
  48. 2026-07-19 14:31 UTCEPSS rescore
  49. 2026-07-19 05:52 UTCOSV refresh
  50. 2026-07-19 02:29 UTCEPSS rescore
  51. 2026-06-14 23:18 UTCEPSS rescore
  52. 2026-06-13 23:00 UTCEPSS rescore
  53. 2026-06-12 23:12 UTCEPSS rescore
  54. 2026-05-27 01:14 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44739?
CVE-2026-44739 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.6, the columnConfigAction endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php passes malicious SQL configuration through CustomReportController:columnConfigAction,…
When was CVE-2026-44739 disclosed?
CVE-2026-44739 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-44739 actively exploited?
CVE-2026-44739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44739?
CVE-2026-44739 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-44739?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44739, 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-44739

Explore →

Is Your Infrastructure Affected by CVE-2026-44739?

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

Start Free Scan →Browse All CVEs