Live › vulnerability › CVE-2026-116796
Go to dashboardHighcharts JS accepts an SVG xlink:href attribute without the allowed-scheme check it applies to href and src. An attacker who controls a chart text option can keep a javascript: URL in exported SVG, and script runs when a user clicks that link in the re-parsed document.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Teams that ship Highcharts 10.3.2 through versions before 11.4.9, 12.6.2 or 13.1.1 and let end users set chart text, then export or server-render that chart as SVG that is later reopened and clicked. Apps that only render charts in the browser from trusted data, or do not export SVG, are less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| highcharts | npm | >= 10.3.2, < 11.4.9 | 11.4.9 |
| highcharts | npm | >= 12.0.0, < 12.6.2 | 12.6.2 |
| highcharts | npm | >= 13.0.0, <= 13.1.0 | 13.1.1 |
npm ls highcharts and look at the Highcharts version in your lockfile.11.4.9, 12.6.2 or 13.1.1, whichever matches your major version.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The filter applied to markup in text options checks href, src and a few similar attributes against an allowed-scheme list, but accepts xlink:href without that check, so an SVG anchor whose xlink:href is a javascript: URL passes the filter, whether or not the option is rendered with useHTML. In the live page the attribute is written without the XLink namespace, so browsers do not treat the anchor as a link there.
The attribute is preserved verbatim in the chart's serialised output: the SVG produced by the exporting module, including the default SVG download, declares the XLink namespace and contains the anchor, and so does the markup of the chart container. Any document that parses that output again, such as the downloaded SVG opened in a browser or a page that inlines exported or server-rendered chart markup, then holds a working link, and an attacker who controls the chart configuration can thereby run script in the origin of that document when a user activates the link.
Exploitation requires that untrusted data reach a text option such as the title, that the chart be exported or its markup be serialised and parsed again, and that a user activate the link.
Drop-in fix for all affected versions (10.3.2 - 13.1.0).
Add the below IIFE to run after Highcharts is loaded, before creating a chart.
!function(t){var e=t&&t.AST;if(e&&"function"==typeof e.filterUserAttributes&&!e.xlinkHrefPatched){var r=e.filterUserAttributes,n=Object.prototype.hasOwnProperty;e.filterUserAttributes=function(t){return t&&n.call(t,"xlink:href")&&!o(t["xlink:href"])&&delete t["xlink:href"],r.call(this,t)},e.xlinkHrefPatched=!0}function o(t){var r=e.allowedReferences||["https://","http://","mailto:","/","../","./","#"];return"string"==typeof t&&r.some(function(e){return 0===t.indexOf(e)})}}(Highcharts);
The patched releases are available from all the usual distribution channels. With npm, upgrade the affected package to the patched version listed above, for example npm install [email protected]. If you load Highcharts from the CDN, use the versioned URLs on code.highcharts.com, for example https://code.highcharts.com/13.1.1/highcharts.js. For more on each installation method, see the installation guide.
This page as .md · .json · in your agent: get_signal("CVE-2026-116796")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.