CVE-2026-118251: Highcharts · `javascript:` URL in credits.href runs script on click
Affects highchartsSource GCVE Database
Not known to be exploited · CVSS 8.4 High : upgrade to 11.4.9 soon.
Data as of 28 Oct 2026, 21:14 UTC
- Patch
- Available – fixed in 11.4.9, 12.6.1, 13.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade highcharts to 11.4.9; highcharts to 12.6.1; highcharts to 13.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmhighcharts | Affected
| Fixed in
|
| npmhighcharts | Affected
| Fixed in
|
| npmhighcharts | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
### Impact 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. ### Workarounds 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. ```js !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); ``` [Live demo & testing](https://jsfiddle.net/BlackLabel/6a09ws1f/) ### Obtaining the patched version 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](https://www.highcharts.com/docs/getting-started/installation).
References
- github.com/highcharts/highcharts/security/advisories/GHSA-5793-x2q3-c3q7 (opens in a new tab)
- github.com/highcharts/highcharts/pull/25315 (opens in a new tab)
- github.com/highcharts/highcharts/commit/9534773d0f41400aac0945bf8aaebc38dfc72aff (opens in a new tab)
- github.com/highcharts/highcharts (opens in a new tab)
- github.com/highcharts/highcharts/releases/tag/v13.1.0 (opens in a new tab)