CVE-2026-116797: Highcharts Grid Pro: cell-renderer `attributes` map written with raw `setAttribute`
Highcharts Grid Pro's input and select cell renderers copy every entry of the `attributes` option onto the element with no name check. If untrusted data reaches the Grid configuration, an attacker can add event-handler attributes that run script in the host page. `@highcharts/grid-pro` 2.0.0 to 3.1.0 and `@highcharts/dashboards` 3.6.0 are affected. Fixed in 3.2.0 and 4.0.0.
Published Oct 28, 2026 · Analysis Nov 1, 2026
What an attacker can do
A column can set cells.renderer.attributes or cells.editMode.renderer.attributes. The input-type renderers write each key and value onto the input or select they create with a raw setAttribute. Nothing stops a key like onfocus or onmouseover, so the value runs as JavaScript in the origin of the page that hosts the Grid. This is a DOM-based XSS.
Timing differs by renderer. A view renderer places the handler on the input rendered in every row of the column, as soon as the Grid renders, so it fires when a user hovers over or focuses one. An edit-mode renderer places it on the input created when a cell enters edit mode, and that input is focused immediately, so a focus handler fires as soon as the user starts editing a cell.
The attacker needs to get untrusted data into the Grid configuration, for example column definitions loaded from a saved user layout, a shared dashboard or an API response. A user must then interact with an input. The script runs with the user's session, so it can read page data and tokens and act as the user. The score is 8.5 under CVSS 4.0. The Pro DataGrid shipped inside the Dashboards package is included.
Who is affected
@highcharts/grid-pro: 2.0.0 through 3.1.0.@highcharts/dashboards: 3.6.0, which bundles the Pro DataGrid.
You are exposed when column configuration, including columnDefaults, comes from a source you do not fully control. Check your install:
npm ls @highcharts/grid-pro @highcharts/dashboardsCDN users should read the version from the script URL.
@highcharts/grid-pro
- Ecosystem
- npm
- Affected
- >= 2.0.0, <= 3.1.0
- Fixed in
- 3.2.0
- Check
npm ls @highcharts/grid-pro
@highcharts/dashboards
- Ecosystem
- npm
- Affected
- = 3.6.0
- Fixed in
- 4.0.0
- Check
npm ls @highcharts/dashboards
How to fix it
Upgrade @highcharts/grid-pro to 3.2.0 and @highcharts/dashboards to 4.0.0.
npm install @highcharts/[email protected]CDN users should switch to a versioned URL. If you cannot upgrade, the advisory gives a script to paste right after importing the Grid module. It deletes any renderer attribute not on an allowlist (autofocus, checked, max, maxlength, min, minlength, multiple, pattern, placeholder, size, step) from column defaults and columns, and hooks loadUserOptions and updateColumn so later updates are scrubbed too.
How to tell if you were hit
Search stored grid configurations, user layouts and API payloads for attributes maps under cells.renderer or cells.editMode.renderer that contain keys starting with on. Check rendered pages for inputs inside the Grid that carry inline event-handler attributes. Review where column definitions come from and whether any of it is user-editable.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
The input-type cell renderers copy every entry of the renderer's attributes option onto the input or select element they create, without checking the attribute names. An attacker who controls the Grid configuration can supply entries under a column's cells.renderer.attributes or cells.editMode.renderer.attributes whose names are event handlers, and those handlers execute in the origin of the page hosting the Grid. A view renderer places the handler on the input rendered in every row of the column as soon as the Grid renders; an edit-mode renderer places it on the input created when a cell enters edit mode, and that input is focused immediately, so a focus handler runs as soon as the user starts editing. Exploitation requires that untrusted data reach the Grid configuration and that a user hover over or focus one of the rendered inputs, or begin editing a cell. The Pro DataGrid that shipped inside the Dashboards package is included.
Workarounds
If your column configuration comes from a source you do not fully control, paste this snippet right after importing the Grid module:
const ALLOWED_RENDERER_ATTRIBUTES = [
'autofocus', 'checked', 'max', 'maxlength', 'min', 'minlength',
'multiple', 'pattern', 'placeholder', 'size', 'step'
];
const scrubColumn = (column) => {
const cells = column?.cells;
for (const renderer of [cells?.renderer, cells?.editMode?.renderer]) {
const attributes = renderer?.attributes;
if (attributes) {
for (const key of Object.keys(attributes)) {
if (!ALLOWED_RENDERER_ATTRIBUTES.includes(key.toLowerCase())) {
delete attributes[key];
}
}
}
}
return column;
};
const scrubOptions = (options) => {
scrubColumn(options?.columnDefaults);
(options?.columns || []).forEach(scrubColumn);
return options;
};
const proto = Grid.Grid.prototype;
const loadUserOptions = proto.loadUserOptions;
proto.loadUserOptions = function (options, ...rest) {
scrubOptions(Grid.defaultOptions);
return loadUserOptions.call(this, scrubOptions(options), ...rest);
};
const updateColumn = proto.updateColumn;
proto.updateColumn = function (columnId, options, ...rest) {
return updateColumn.call(this, columnId, scrubColumn(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/[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.
Questions
- Does the user have to click something?
They must hover over or focus a rendered input, or start editing a cell. For an edit-mode renderer, the new input is focused at once, so a focus handler fires as soon as editing starts.
- Is Dashboards affected?
Yes, version 3.6.0 of
@highcharts/dashboards, because it ships the Pro DataGrid. Version 4.0.0 is patched.- Is there a workaround besides upgrading?
Yes. The advisory provides a script that removes every renderer attribute outside an allowlist, applied to column defaults, columns and later updates.
- Is CVE-2026-116797 exploited in the wild?
No source says so, and it is not in CISA's KEV catalog.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-118242
Highcharts Grid: custom icon definition objects written with raw `setAttribute` on `<path>`
high8.5Oct 28, 2026CVE-2026-118243
Highcharts Dashboards: `__proto__` data table id writes sync listeners to `Object.prototype`
medium5.3Oct 28, 2026CVE-2026-118245
Highcharts Dashboards: `chartConstructor` is an unchecked lookup into the Highcharts namespace
high8.6Oct 28, 2026CVE-2026-118247
Highcharts Dashboards / Grid Pro: `DataTable.setCell` and column writers treat `__proto__` as an existing column.
medium6.9Oct 28, 2026CVE-2026-118252
Highcharts Dashboards parses sidebar component labels as HTML
high8.4Oct 28, 2026CVE-2026-118253
Highcharts Dashboards parses fullscreen labels as HTML
high8.4Oct 28, 2026
