Highcharts Grid: custom icon definition objects written with raw `setAttribute` on `<path>`
CVE-2026-118242 · GHSA-6g3c-p4fg-xv47 · published 28 Oct 2026
How serious is it
- Severity: high, CVSS score 8.5 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-118242?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
@highcharts/grid-lite(npm) >= 2.3.0, <= 3.1.0@highcharts/grid-pro(npm) >= 2.3.0, <= 3.1.0
How to check
- Run
npm ls @highcharts/grid-litein your project to see the installed version, including copies pulled in by other packages. - Run
npm ls @highcharts/grid-proin your project to see the installed version, including copies pulled in by other packages. - Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
- Or run
npx shippable-dev scan localhost:3000in your project folder. It reads your lockfile and flags this vulnerability along with every other known one.
How to fix
Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
- On >= 2.3.0, <= 3.1.0: Upgrade
@highcharts/grid-liteto 3.2.0 or later, commit the lockfile and redeploy. - On >= 2.3.0, <= 3.1.0: Upgrade
@highcharts/grid-proto 3.2.0 or later, commit the lockfile and redeploy. - If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
### Impact
A custom icon supplied under `rendering.icons` as an icon definition object is built by creating an SVG path for each of its child entries and setting every key of that entry as an attribute of the path, without filtering the attribute names; only the string form of the option is passed through the markup allow-list. An attacker who controls the Grid configuration can therefore supply child entries whose keys name event handlers, and those handlers execute in the origin of the page hosting the Grid. Custom icons take precedence over the built-in ones, so the attacker can replace icons that render without any further configuration, such as the sort icon shown in every column header by default and the pagination controls where pagination is enabled, and does not need any reference to a custom icon name. Exploitation requires that untrusted data reach the Grid configuration and that a user hover over or activate an affected icon.
### Workarounds
If your Grid configuration comes from a source you do not fully control, paste this snippet right after importing the Grid module:
```ts
(function () {
const GridNS = typeof Grid !== 'undefined' ? Grid : undefined;
const GridClass = GridNS && GridNS.Grid;
if (!GridClass || !GridClass.prototype.loadUserOptions) {
return; // Grid not loaded
}
const allowedPathAttributes = [
'd',
'fill',
'opacity',
'stroke',
'stroke-width',
'stroke-linecap',
'stroke-linejoin',
'transform'
];
const originalLoadUserOptions = GridClass.prototype.loadUserOptions;
function sanitizeIconValue(value) {
if (!value || typeof value === 'string') {
return value;
}
const children = value.children || [];
const sanitizedChildren = [];
for (let i = 0; i < children.length; i++) {
const child = children[i] || {};
const clean = {};
for (let j = 0; j < allowedPathAttributes.length; j++) {
const attr = allowedPathAttributes[j];
if (child[attr] !== undefined && child[attr] !== null) {
clean[attr] = child[attr];
}
}
sanitizedChildren.push(clean);
}
return {
width: value.width,
height: value.height,
viewBox: value.viewBox,
fill: value.fill,
children: sanitizedChildren
};
}
function sanitizeIconsMap(icons) {
if (!icons) {
return icons;
}
const out = {};
for (const key in icons) {
if (Object.prototype.hasOwnProperty.call(icons, key)) {
out[key] = sanitizeIconValue(icons[key]);
}
}
return out;
}
GridClass.prototype.loadUserOptions = function (newOptions) {
if (
newOptions &&
newOptions.rendering &&
newOptions.rendering.icons
) {
newOptions.rendering.icons = sanitizeIconsMap(
newOptions.rendering.icons
);
}
return originalLoadUserOptions.apply(this, arguments);
};
}());
```
### 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).
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- github.com/highcharts/highcharts/security/advisories/GHSA-6g3c-p4fg-xv47
- nvd.nist.gov/vuln/detail/CVE-2026-118242
- github.com/highcharts/highcharts/commit/8fc970658fee6601625b42da29d27c3ef7c45e30
- github.com/advisories/GHSA-6g3c-p4fg-xv47
- github.com/highcharts/highcharts
Merged from GitHub Advisory Database, OSV. Last updated 29 Oct 2026. All vulnerabilities · RSS · JSON