A flaw has been found in DataEase up to 3.0.0. The impacted element is the function Utils.buildCalcField of the file io/dataease/engine/utils/Utils.java. This manipulation of the argument calculated field causes sql injection. It is possible to initiate the attack remotely. The exploit has been published and may be used. Patch name: 8509e218e6c1f0080eee9e379f269b2104785ef7. It is recommended to apply a patch to fix this issue.
CVE-2026-108824
MEDIUMPre-NVD 6.36.3Trending — 5 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-10-12. A secondary CVSS source baseline 6.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source
6.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.4%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3MEDIUMhigh confidence
- EG Risk
- 44EG Risk 44/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)Severity63% × 45%The EG Score, 6.3 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 or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.4%
- EPSS %ILE
- 29th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (5)
Auto-updated Oct 12, 2026🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
Web page
GitHub - dataease/dataease: 🔥 人人可用的开源 BI 工具，数据可视化神器。An open-source BI tool alternative to Tableau. · GitHub
https://github.com/dataease/dataease/Web page🟡 PoC Available
DataEase-Authenticated-SQL-Injection-/README.md at main · k4z01/DataEase-Authenticated-SQL-Injection- · GitHub
https://github.com/k4z01/DataEase-Authenticated-SQL-Injection-/blob/main/README.mdGitHub commit
commit 8509e218e6c1 (dataease/dataease)
Fix landed in dataease/dataease commit 8509e218e6c1 — awaiting tagged release
https://github.com/dataease/dataease/commit/8509e218e6c1f0080eee9e379f269b2104785ef7GitHub pull request
fix(auth): 校验分享令牌并约束分享资源访问
Fix merged in dataease/dataease PR #19285 on 2026-09-29 — awaiting tagged release
https://github.com/dataease/dataease/pull/19285Web page🟡 PoC Available
DataEase authenticated SQL injection and missing authorization on /de2api/datasetData/previewData via the calculated-field expression. · GitHub
https://gist.github.com/k4z01/536b77dfe537e84ca1047c94cc36ef22Vendor Advisories for CVE-2026-108824(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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.
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-13 15:27 UTCEG score recompute
- 2026-10-13 15:26 UTCGHSA enrichmentGHSA-538j-pf96-87xg · GitHub severity LOW · GitHub CVSS 6.3
- 2026-10-13 15:24 UTCNVD updateCVSS v4 → 2.1
- 2026-10-13 15:07 UTCEG score recompute
- 2026-10-13 15:07 UTCGHSA enrichmentGHSA-538j-pf96-87xg · GitHub severity LOW · GitHub CVSS 6.3
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 11:26 UTCEG score recompute
- 2026-10-12 11:24 UTCNVD updateCVSS v4 → 2.1
- 2026-10-12 10:35 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
- 2026-10-12 10:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108824?
CVE-2026-108824 is a medium-severity vulnerability; its CVE record was published on October 12, 2026. A flaw has been found in DataEase up to 3.0.0. The impacted element is the function Utils.buildCalcField of the file io/dataease/engine/utils/Utils.java. This manipulation of the argument calculated field causes sql injection. It is possible to initiate the attack remotely. The exploit has been…
When was the CVE record for CVE-2026-108824 published?
The CVE record for CVE-2026-108824 was published on October 12, 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 October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-108824 actively exploited?
CVE-2026-108824 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108824?
CVE-2026-108824 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108824?
An upstream fix for CVE-2026-108824 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-108824 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108824
Is Your Infrastructure Affected by CVE-2026-108824?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.