# CVE-2026-90529: DataEase Symbolic Map symbolic-map.ts buildTooltip cross site scripting

> Remote attackers can execute arbitrary scripts via the Symbolic Map tooltip background color parameter in DataEase.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-xvhf-cv8g-xhpr

## What is CVE-2026-90529?

CVE-2026-90529 is a medium-severity cross-site scripting vulnerability in DataEase, published on 13 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in DataEase up to 2.10.25/2.10.26. Affected by this issue is the function buildTooltip of the file core/core-frontend/src/views/chart/components/js/panel/charts/map/symbolic-map.ts of the component Symbolic Map. Such manipulation of the argument canvasViewInfo[*].customAttr.tooltip.backgroundColor leads to cross site scripting. The attack may be performed from remote. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-90529?


## How do I fix CVE-2026-90529?

No fix has been published for CVE-2026-90529 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90529 being exploited?

There is no known exploitation of CVE-2026-90529 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90529 and fix it if it is affected.

What it is: CVE-2026-90529 is a medium-severity cross-site scripting vulnerability in DataEase, published on 13 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-90529 in the wild and no public exploit code.

Affected product: DataEase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90529/ (Markdown: https://insights.sbomify.com/CVE-2026-90529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90529
- OSV: https://osv.dev/vulnerability/CVE-2026-90529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90529/
Summaries are generated and may contain mistakes; the official description above is the record.