Live › vulnerability › CVE-2026-118251
Go to dashboardHighcharts JS assigns the credits link URL straight to the window location without checking the scheme. An attacker who controls the chart configuration can supply a javascript: URL that runs script in the hosting page's origin when a user clicks the credits label.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 19:34 UTC. All times on this page are UTC.
Pages that render Highcharts charts from configuration an attacker can influence, such as user-saved dashboards, shared chart embeds or charts built from stored content. Exposure needs a user to click the credits label. Applications that only render charts from fixed, server-controlled configuration are much less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| highcharts | npm | < 11.4.9 | 11.4.9 |
| highcharts | npm | >= 12.0.0, < 12.6.1 | 12.6.1 |
| highcharts | npm | >= 13.0.0, <= 13.0.2 | 13.1.0 |
npm ls highcharts (or the highcharts entry in package.json and lockfile)credits in chart configuration and look for any chart config built from user-supplied or stored datahighcharts to 11.4.9, 12.6.1 or 13.1.0 (Highcharts Stock, Maps and Gantt ship from the same package)credits.hrefEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A credits.href value beginning with javascript: is assigned to the window location when the credits label is clicked, without being checked against an allowed-scheme list. An attacker who controls the chart configuration can therefore run script in the origin of the page hosting the chart. Exploitation requires that untrusted data reach the chart configuration and that a user click the credits label. Charts built with Highcharts Stock, Maps and Gantt are included, since those ship from the same package as Core.
Drop-in fix - for any versions affected (5.0.0-13.0.2). Add the below IIFE to run after Highcharts is loaded, but before a chart is created.
!function(t){if(t&&t.Chart&&!t.Chart.prototype.creditsHrefPatched){var r=t.Chart.prototype,e=r.addCredits;r.addCredits=function(n){var o=t.merge(!0,this.options.credits,n);return o&&o.href&&!c(o.href)&&delete o.href,e.call(this,o)},r.creditsHrefPatched=!0}function c(r){var e=t.AST&&t.AST.allowedReferences||["https://","http://","mailto:","/","../","./","#"];return"string"==typeof r&&e.some(function(t){return 0===r.indexOf(t)})}}(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 highcharts@ 13.1.0. If you load Highcharts from the CDN, use the versioned URLs on code.highcharts.com, for example https://code.highcharts.com/13.1.0/highcharts.js. For more on each installation method, see the installation guide.
This page as .md · .json · in your agent: get_signal("CVE-2026-118251")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.