GHSA-6G3C-P4FG-XV47
Vulnerability from github – Published: 2026-10-28 19:55 – Updated: 2026-10-28 19:55Impact
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:
(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.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.1.0"
},
"package": {
"ecosystem": "npm",
"name": "@highcharts/grid-lite"
},
"ranges": [
{
"events": [
{
"introduced": "2.3.0"
},
{
"fixed": "3.2.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 3.1.0"
},
"package": {
"ecosystem": "npm",
"name": "@highcharts/grid-pro"
},
"ranges": [
{
"events": [
{
"introduced": "2.3.0"
},
{
"fixed": "3.2.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-118242"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-28T19:55:46Z",
"nvd_published_at": "2026-10-28T18:17:14Z",
"severity": "HIGH"
},
"details": "### Impact\nA 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.\n\n### Workarounds\nIf your Grid configuration comes from a source you do not fully control, paste this snippet right after importing the Grid module:\n\n```ts\n(function () {\n const GridNS = typeof Grid !== \u0027undefined\u0027 ? Grid : undefined;\n const GridClass = GridNS \u0026\u0026 GridNS.Grid;\n\n if (!GridClass || !GridClass.prototype.loadUserOptions) {\n return; // Grid not loaded\n }\n\n const allowedPathAttributes = [\n \u0027d\u0027,\n \u0027fill\u0027,\n \u0027opacity\u0027,\n \u0027stroke\u0027,\n \u0027stroke-width\u0027,\n \u0027stroke-linecap\u0027,\n \u0027stroke-linejoin\u0027,\n \u0027transform\u0027\n ];\n\n const originalLoadUserOptions = GridClass.prototype.loadUserOptions;\n\n function sanitizeIconValue(value) {\n if (!value || typeof value === \u0027string\u0027) {\n return value;\n }\n\n const children = value.children || [];\n const sanitizedChildren = [];\n\n for (let i = 0; i \u003c children.length; i++) {\n const child = children[i] || {};\n const clean = {};\n\n for (let j = 0; j \u003c allowedPathAttributes.length; j++) {\n const attr = allowedPathAttributes[j];\n if (child[attr] !== undefined \u0026\u0026 child[attr] !== null) {\n clean[attr] = child[attr];\n }\n }\n\n sanitizedChildren.push(clean);\n }\n\n return {\n width: value.width,\n height: value.height,\n viewBox: value.viewBox,\n fill: value.fill,\n children: sanitizedChildren\n };\n }\n\n function sanitizeIconsMap(icons) {\n if (!icons) {\n return icons;\n }\n\n const out = {};\n for (const key in icons) {\n if (Object.prototype.hasOwnProperty.call(icons, key)) {\n out[key] = sanitizeIconValue(icons[key]);\n }\n }\n return out;\n }\n\n GridClass.prototype.loadUserOptions = function (newOptions) {\n if (\n newOptions \u0026\u0026\n newOptions.rendering \u0026\u0026\n newOptions.rendering.icons\n ) {\n newOptions.rendering.icons = sanitizeIconsMap(\n newOptions.rendering.icons\n );\n }\n\n return originalLoadUserOptions.apply(this, arguments);\n };\n}());\n```\n\n### Obtaining the patched version\nThe 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).",
"id": "GHSA-6g3c-p4fg-xv47",
"modified": "2026-10-28T19:55:46Z",
"published": "2026-10-28T19:55:46Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/highcharts/highcharts/security/advisories/GHSA-6g3c-p4fg-xv47"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118242"
},
{
"type": "WEB",
"url": "https://github.com/highcharts/highcharts/commit/8fc970658fee6601625b42da29d27c3ef7c45e30"
},
{
"type": "PACKAGE",
"url": "https://github.com/highcharts/highcharts"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Highcharts Grid: custom icon definition objects written with raw `setAttribute` on `\u003cpath\u003e`"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.