High

Highcharts Grid: custom icon definition objects written with raw `setAttribute` on `<path>`

  • Disclosed: 28.10.2026
  • Updated: 04.11.2026 10:00

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.).

What to do

Upgrade @highcharts/grid-lite and @highcharts/grid-pro to version 3.2.0 or later. If upgrading is not immediately possible, apply the workaround snippet right after importing the Grid module.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package @highcharts/grid-lite >= 2.3.0, < 3.2.0 3.2.0
npm package @highcharts/grid-pro >= 2.3.0, < 3.2.0 3.2.0

References

CVSS score -
CVSS vector
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
Weakness (CWE)
CWE-79
Platform
npm
Package
@highcharts/grid-lite, @highcharts/grid-pro
Disclosed
28.10.2026
Updated
04.11.2026 10:00

Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.

OSV / GitHub Advisory Database - GHSA-6g3c-p4fg-xv47 - CC BY 4.0

Vulnerability history: @highcharts/grid-pro

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
4
First → latest
10.2026 10.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 3
  • Medium 1

Disclosures per year

  1. 2026: 4
  1. Highcharts Grid: custom icon definition objects written with raw `setAttribute` on `<path>` this entry
    High CVE-2026-118242 >= 2.3.0, < 3.2.0 3.2.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.