CVE-2026-116797: Highcharts Grid Pro: cell-renderer `attributes` map written with raw `setAttribute`
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:
ts const ALLOWEDRENDERERATTRIBUTES = [ '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 (!ALLOWEDRENDERERATTRIBUTES.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/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.
Other sources
Highcharts JS is a JavaScript charting library based on SVG. From 2.0.0 until 3.2.0, Highcharts Grid Pro input renderers copy the cells.renderer.attributes and cells.editMode.renderer.attributes maps to input or select elements with raw setAttribute calls. An attacker who controls column configuration can add event-handler attributes to every rendered row or to the control created when a cell enters edit mode. Script then runs in the hosting page origin when a user hovers over or focuses an input or begins editing. This issue is fixed in Grid Pro 3.2.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@highcharts/dashboardsto a version that resolves this vulnerability.Fixed in 4.0.0 - Upgrade
Upgrade
npm/@highcharts/grid-proto a version that resolves this vulnerability.Fixed in 3.2.0 - Upgrade
Upgrade
@highcharts/grid-liteto a version that resolves this vulnerability.Fixed in 3.2.0 - Compensating control
If column configuration is not fully trusted, add the provided scrubber immediately after importing the Grid module. It must inspect cells.renderer.attributes and cells.editMode.renderer.attributes and delete every attribute whose name is not in the allowlist: autofocus, checked, max, maxlength, min, minlength, multiple, pattern, placeholder, size, and step.
Event History
Frequently Asked Questions
Who is exposed to this issue?
Applications using Highcharts Grid Pro versions from 2.0.0 through versions before 3.2.0 are exposed if an attacker can control column configuration, including renderer attribute maps.
What does an attacker need to exploit it?
The attacker needs control of cells.renderer.attributes or cells.editMode.renderer.attributes in column configuration. They can supply event-handler attributes that are copied to rendered input or select elements.
When does malicious code execute?
Code executes in the hosting page's origin when a user hovers over or focuses an affected input, or when a cell enters edit mode and its control is created.
What version fixes the issue?
Grid Pro 3.2.0 fixes the issue.