Live › vulnerability › CVE-2026-118255
Go to dashboardHighcharts Grid applies a configured credits.href to the credits link without checking the URL scheme, so a javascript: URL is accepted. When a user activates that link, the script runs in the hosting page's origin with access to the application's data and session.
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.
Applications that use Highcharts Grid from version 2.0.0 up to 3.2.0 and let someone other than the developer control the Grid configuration, such as saved dashboards or user-editable chart settings, are exposed. Applications where the configuration is fixed in code by developers are much less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @highcharts/dashboards | npm | >= 3.2.0, <= 3.6.0 | 4.0.0 |
| @highcharts/grid-pro | npm | >= 2.0.0, <= 3.1.0 | 3.2.0 |
npm ls highcharts-grid or grep -i highcharts-grid package-lock.jsoncredits.href from user-supplied or stored configuration3.2.0 or latercredits.hrefEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
Paste in after the Grid Pro module is imported, before a Grid is created.
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);
};
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/[email protected]. If you load Highcharts Grid from a CDN, use a versioned URL, for example https://cdn.jsdelivr.net/npm/@highcharts/[email protected]/grid-lite.js. For more on each installation method, see the installation guide.
This page as .md · .json · in your agent: get_signal("CVE-2026-118255")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.