# CVE-2026-72751: Stored Cross-Site Scripting in CTI-Transmute Conversion Graph via Malicious STIX/MISP Content

> Attackers can execute arbitrary JavaScript in the CTI-Transmute graph UI by injecting malicious HTML into STIX or MISP content fields.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-p8v9-h3m5-mvj9

## What is CVE-2026-72751?

CVE-2026-72751 is a medium-severity cross-site scripting vulnerability in misp cti-transmute, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CTI-Transmute is affected by a stored cross-site scripting (XSS) vulnerability in the conversion graph used to visualise converted MISP and STIX content.

Attacker-controlled values originating from converted CTI data were passed to multiple HTML-parsing sinks in the graph user interface without sufficient neutralisation. In particular, node labels, node sublabels, edge labels, node properties, edge properties, and node types could contain crafted HTML or JavaScript content.

The Pivotick graph library renders some of these values through HTML-parsing operations. Consequently, a malicious value such as an HTML element containing an event handler could be interpreted as markup rather than displayed as plain text. The first remediation explicitly notes that Pivotick rendered node and edge labels as HTML and therefore introduced escaping before data was handed to the graph renderer.

A separate vulnerable sink was present in the Open raw JSON functionality. The raw object associated with a graph node was inserted into a new document using document.write() and an interpolated HTML string. Crafted JSON content could therefore break out of the intended <pre> element and inject executable markup. The fix replaced this construction with DOM APIs and assigns the JSON using textContent.

The initial correction did not cover all Pivotick rendering paths. A subsequent patch addressed additional XSS vectors in the graph properties panel. Values derived from the original CTI object—including property names, property values, hash algorithm names, child attributes, edge properties, and STIX object types—could still reach Pivotick's HTML resolver. According to the patch, Pivotick's tryResolveHTMLElement processes string values using template.innerHTML, allowing malicious markup to execute when a graph node is hovered over or selected.

The complete remediation therefore:

  *  HTML-escapes node labels, node sublabels, and edge labels before they are passed to Pivotick.
  *  Restricts graph node type values to a safe identifier character set.
  *  Wraps node and edge property values in DOM elements populated through textContent, preventing Pivotick from treating attacker-controlled strings as HTML.
  *  Replaces the raw-JSON popup's interpolated document.write() with DOM construction and textContent.

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

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


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

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

## Is CVE-2026-72751 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72751 is a medium-severity cross-site scripting vulnerability in misp cti-transmute, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-72751 in the wild and no public exploit code.

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

## Sources

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

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