CVE-2026-118255: Highcharts Grid · `javascript:` URL in credits.href runs script on click
Affects @highcharts/dashboardsSource GCVE Database
Not known to be exploited · CVSS 8.4 High : upgrade to 4.0.0 soon.
Data as of 28 Oct 2026, 21:14 UTC
- Patch
- Available – fixed in 4.0.0, 3.2.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/dashboards to 4.0.0; @highcharts/grid-pro to 3.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@highcharts/dashboards | Affected
| Fixed in
|
| npm@highcharts/grid-pro | 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 An attacker who controls the Grid configuration can set `credits.href` to a `javascript:` URL. The value is not validated against an allowed-scheme list before it is applied to the credits link, so activating that link runs attacker-supplied script in the origin of the page hosting the Grid. Exploitation requires that untrusted data reach the Grid configuration and that a user activate the credits link. Script running this way has the same access to page data, storage and session state as the hosting application. ### Workarounds Paste in after the Grid Pro module is imported, before a Grid is created. ```javascript const { AST } = Grid; function sanitize(options) { const credits = options && options.credits; if (credits && typeof credits.href === 'string') { const filtered = AST.filterUserAttributes({ href: credits.href }); if (!filtered.href) { delete credits.href; } } return options; } // Both Grid.grid() and grid.update() funnel through loadUserOptions, so one // hook covers both entry points. const { prototype } = Grid.Grid; const loadUserOptions = prototype.loadUserOptions; prototype.loadUserOptions = function (options, ...rest) { sanitize(options); return loadUserOptions.call(this, options, ...rest); }; ``` ### 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/grid-lite@3.2.0`. If you load Highcharts Grid from a CDN, use a versioned URL, for example `https://cdn.jsdelivr.net/npm/@highcharts/grid-lite@3.2.0/grid-lite.js`. For more on each installation method, see the [installation guide](https://www.highcharts.com/docs/grid/installation).
References
- github.com/highcharts/highcharts/security/advisories/GHSA-6hgp-fmhr-mrg4 (opens in a new tab)
- github.com/highcharts/highcharts/pull/25351 (opens in a new tab)
- github.com/highcharts/highcharts/commit/45b74403acafbe9f621c4a343506721d9129e991 (opens in a new tab)
- github.com/highcharts/highcharts (opens in a new tab)
- github.com/highcharts/highcharts/releases/tag/grid-v3.2.0 (opens in a new tab)