# CVE-2026-117494: Multiple vulnerabilities in Sisense’s Cloud BI Platform


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-mjhm-mj37-2hg8

## What is CVE-2026-117494?

CVE-2026-117494 is a high-severity vulnerability in Sisense Cloud BI Platform, published on 27 Oct 2026. 

### Official description

Cross-Site Scripting (XSS) in the processing of SVG images submitted to the /api/v2/ai/sessions API in the format data:image/svg+xml;base64. Script tags embedded in the SVG are processed when the content is rendered in the assistant window, allowing JavaScript to be executed and the displayed content to be altered.

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

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


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

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

## Is CVE-2026-117494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-117494 is a high-severity vulnerability in Sisense Cloud BI Platform, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117494 in the wild and no public exploit code.

Affected product: Sisense Cloud BI Platform. 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-117494/ (Markdown: https://insights.sbomify.com/CVE-2026-117494/index.md)
```

## Sources

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

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