# CVE-2026-41518: Chartbrew has a stored DOM XSS via Chart Tooltip innerHTML (ChartDatasetConfig.legend)

> Authenticated users can inject malicious scripts into chart tooltips, leading to code execution for all dashboard viewers.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **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:** 4 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-6q2j-365c-7gqf

## What is CVE-2026-41518?

CVE-2026-41518 is a high-severity cross-site scripting vulnerability in chartbrew, published on 4 Jun 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

Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. In versions 4.9.0 through 5.0.0, an authenticated user with project-editor permissions can store arbitrary HTML/JavaScript in the `ChartDatasetConfig.legend` field. The payload is persisted verbatim in the database, propagated through the Chart.js rendering pipeline, and injected into the tooltip DOM element via an unguarded `innerHTML` assignment in `ChartTooltip.js`. Every unauthenticated viewer of the public dashboard triggers JavaScript execution on page load — no hover interaction is required. Browser-based Playwright verification confirmed `alert('localhost')` fires immediately and `<img src="x" onerror="alert(document.domain)">` is present in the `#chartjs-tooltip` DOM element. Version 5.0.1 contains a fix.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-41518 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41518 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41518 is a high-severity cross-site scripting vulnerability in chartbrew, published on 4 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41518 exists.

Affected product: chartbrew. 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-41518/ (Markdown: https://insights.sbomify.com/CVE-2026-41518/index.md)
```

## Sources

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

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