CVE-2026-102756: DataEase: stored XSS via chart axis label tooltip

Q: Is CVE-2026-102756 actively exploited?

No confirmed active exploitation of CVE-2026-102756 has been reported, but organizations should still patch proactively.

Q: What systems are affected by CVE-2026-102756?

This vulnerability affects the following AI/ML architecture patterns: BI and data visualization dashboards, analytics front-ends for ML data, multi-user data exploration platforms.

Q: What is the CVSS score for CVE-2026-102756?

No CVSS score has been assigned yet.

MEDIUMCISA: TRACK*

Published October 14, 2026

CISO Take

DataEase versions before 2.10.26 contain a stored cross-site scripting flaw in which an HTML-bearing chart dimension value is written into a tooltip via innerHTML, so attacker-controlled JavaScript runs in a victim's session when they hover a truncated axis label. Exploitation needs an authenticated user with dataset and chart editing rights plus a victim who opens the dashboard and hovers the label, which limits the likelihood. There is no CVSS or EPSS data yet, the CVE is not in CISA KEV, and no public exploit or Nuclei template exists. The real exposure is session hijack of higher-privileged DataEase users, such as admins, who can reach connected data sources. Upgrade to 2.10.26 or later, and review who holds dataset and chart edit permissions in the meantime.

Sources:NVDGitHub AdvisoryATLASdataease.io

What is the risk?

Medium. Exploitation requires authentication with edit rights and a victim interacting with the dashboard (hover), so it is not trivially mass-exploitable. The impact is arbitrary script execution in the victim's DataEase session, which can expose dashboards, dataset contents and connected data source credentials, and allow actions as that user. Scope is raised by shared dashboards and privilege differences between the editor and the viewer. No active exploitation, KEV listing, public exploit or scanner template is known, and EPSS and CVSS are not yet available.

How does the attack unfold?

Initial Access

The attacker uses a valid account with dataset and chart editing rights.

AML.T0012

Payload Injection

The attacker stores an HTML payload in a dimension value of a bar-horizontal chart with a label length limit set.

Execution

A victim hovers over the truncated axis label and the tooltip renders the full value through innerHTML, running the script.

AML.T0011

Impact

The script hijacks the victim's session to read datasets, modify content or reach connected data sources.

Initial Access

The attacker uses a valid account with dataset and chart editing rights.

AML.T0012

Payload Injection

The attacker stores an HTML payload in a dimension value of a bar-horizontal chart with a label length limit set.

Execution

A victim hovers over the truncated axis label and the tooltip renders the full value through innerHTML, running the script.

AML.T0011

Impact

The script hijacks the victim's session to read datasets, modify content or reach connected data sources.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
dataease	—	—	No patch

Do you use dataease? You're affected.

How severe is it?

CVSS 3.1

N/A

EPSS

0.4%

chance of exploitation in 30 days

Higher than 29% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

Exploit Available

Exploitation: MEDIUM

Sophistication

Trivial

Exploitation Confidence

medium

○CISA SSVC: Public PoC

Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What should I do?

1 step

1) Upgrade DataEase to 2.10.26 or later (fix commit 8cc4dbd). 2) Until patched, restrict dataset field and chart editing rights to trusted users and audit existing bar-horizontal charts for dimension values containing HTML or script tags. 3) Search dataset dimension values for markers such as '<script', 'onerror=' and 'onload=' and clean any hits. 4) Apply a strict Content-Security-Policy that blocks inline scripts, and set session cookies to HttpOnly and SameSite. 5) Review DataEase audit logs for unexpected dataset or chart edits and rotate credentials of connected data sources if suspicious activity is found.

What does CISA's SSVC say?

DecisionTrack*

Exploitationpoc

AutomatableNo

Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Code ExecutionData LeakageFrameworkAML.T0011- User Execution AML.T0012- Valid Accounts

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.6.2.6-AI system operation and monitoring

NIST AI RMF

MANAGE 2.3-Response to previously unknown risks and vulnerabilities

OWASP LLM Top 10

LLM05-Improper Output Handling

Frequently Asked Questions

What is CVE-2026-102756?

Is CVE-2026-102756 actively exploited?

No confirmed active exploitation of CVE-2026-102756 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-102756?

1) Upgrade DataEase to 2.10.26 or later (fix commit 8cc4dbd). 2) Until patched, restrict dataset field and chart editing rights to trusted users and audit existing bar-horizontal charts for dimension values containing HTML or script tags. 3) Search dataset dimension values for markers such as '<script', 'onerror=' and 'onload=' and clean any hits. 4) Apply a strict Content-Security-Policy that blocks inline scripts, and set session cookies to HttpOnly and SameSite. 5) Review DataEase audit logs for unexpected dataset or chart edits and rotate credentials of connected data sources if suspicious activity is found.

What systems are affected by CVE-2026-102756?

This vulnerability affects the following AI/ML architecture patterns: BI and data visualization dashboards, analytics front-ends for ML data, multi-user data exploration platforms.

What is the CVSS score for CVE-2026-102756?

No CVSS score has been assigned yet.

What is the AI security impact?

Affected AI Architectures

BI and data visualization dashboardsanalytics front-ends for ML datamulti-user data exploration platforms

MITRE ATLAS Techniques

AML.T0011User Execution

AML.T0012Valid Accounts

Compliance Controls Affected

ISO 42001: A.6.2.6

NIST AI RMF: MANAGE 2.3

OWASP LLM Top 10: LLM05

What are the technical details?

Original Advisory

DataEase is an open source data visualization and analysis tool. Prior to 2.10.26, authenticated users who can edit dataset fields and chart configuration can store an HTML-bearing dimension value in a bar-horizontal chart. When lengthLimit truncates the category axis label, configAxisLabelLengthLimit in core/core-frontend/src/views/chart/components/js/panel/common/common_antv.ts retrieves the full label and assigns it to the g2-tooltip-title element through innerHTML. A victim who opens the dashboard and hovers the truncated label can execute attacker-controlled JavaScript in the victim's DataEase session. This issue is fixed in version 2.10.26.

Exploitation Scenario

A low-privileged analyst with chart editing rights adds a dimension value containing an HTML payload, such as an img tag with an onerror handler, to a dataset used by a bar-horizontal chart and sets a short label length limit so the label is truncated. The analyst shares the dashboard with an administrator. When the administrator hovers over the truncated category label, the full value is inserted into the tooltip title via innerHTML and the payload runs in the administrator's session. The script then calls DataEase APIs to read datasets and data source configurations, or creates a new privileged account, giving the attacker access to the underlying analytics data.

Weaknesses (CWE)

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'): The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

[Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
[Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.