CVE-2026-44741

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.4%, top 72% 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.8EG
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.8Exploit: Elevated riskExposed: 0

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

Pimcore's Admin Classic Bundle provides a Backend UI for Pimcore. Versions prior to 2.3.6 and 1.7.18 have a SQL injection vulnerability in Pimcore's translation grid date filter — the user-supplied property field from the filter JSON is interpolated directly into a UNIX_TIMESTAMP(DATE(FROM_UNIXTIME(...))) SQL expression without parameterization or allowlist validation. Versiosn 2.3.6 and 1.7.18 fix the issue.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 12, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

2.3.6

Patch available: pimcore/admin-ui-classic-bundle v2.3.6

https://github.com/pimcore/admin-ui-classic-bundle/releases/tag/v2.3.6
github_commit Patch Available

commit 80e57a23d9e1 (pimcore/admin-ui-classic-bundle)

Patch available: pimcore/admin-ui-classic-bundle v2.3.6 (contains commit 80e57a23d9e1)

https://github.com/pimcore/admin-ui-classic-bundle/commit/80e57a23d9e19574eddfe9b08e8f26785b2b0d90
github_pr Patch Available

[Security]: Update unserialize to use allowed_classes option in Dashboard

Patch available: pimcore/admin-ui-classic-bundle v2.3.6 (PR #1111 merged 2026-05-19)

https://github.com/pimcore/admin-ui-classic-bundle/pull/1111
github Patch Available🟡 PoC Available

SQL Injection in Translation Grid Date Filter via Unsanitized Property Parameter · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-h4ph-crvj-9h92

Vendor Advisories for CVE-2026-44741(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/admin-ui-classic-bundle1.4.0 ... v1.7.9 (67 versions)1.7.18—

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 20 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 01:30 UTCEPSS rescore
  10. 2026-08-14 01:39 UTCEG score recompute
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 18:19 UTCEG score recompute
  13. 2026-08-12 18:17 UTCEG score recompute
  14. 2026-07-31 08:20 UTCEG score recompute
  15. 2026-07-29 16:22 UTCEG score recompute
  16. 2026-07-23 03:15 UTCEG score recompute
  17. 2026-06-14 23:18 UTCEPSS rescore
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-05-27 01:14 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44741?
CVE-2026-44741 is a high vulnerability published on May 27, 2026. Pimcore's Admin Classic Bundle provides a Backend UI for Pimcore. Versions prior to 2.3.6 and 1.7.18 have a SQL injection vulnerability in Pimcore's translation grid date filter — the user-supplied property field from the filter JSON is interpolated directly into a…
When was CVE-2026-44741 disclosed?
CVE-2026-44741 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44741 actively exploited?
CVE-2026-44741 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 71.7% of all scored CVEs.
What is the CVSS score of CVE-2026-44741?
CVE-2026-44741 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44741?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44741, 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-44741

Explore →

Is Your Infrastructure Affected by CVE-2026-44741?

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

Start Free Scan →Browse All CVEs