CVE-2026-118254: Highcharts Grid parses pagination language options as HTML
Impact The pagination language strings are written into the DOM as markup rather than as text. An attacker who controls those language options can supply elements carrying event handlers, and those handlers execute in the origin of the page hosting the Grid when the pagination controls render. Exploitation requires that untrusted data reach the Grid language configuration and that pagination be enabled on the Grid.
Workarounds Run this once after loading the Grid, before creating any grid: javascript { const Pagination = Grid.Pagination;
const escapeLang = (pagination) => { const lang = pagination.lang; if (!lang) { return; }
for (const key of ['pageInfo', 'pageSizeLabel']) { if (typeof lang[key] === 'string') { lang[key] = lang[key].replace(/</g, '<'); } } };
for (const name of ['updatePageInfo', 'renderPageSizeSelector']) { const original = Pagination.prototype[name];
Pagination.prototype[name] = function (...args) { escapeLang(this); return original.apply(this, args); }; } }
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 writes pagination language strings into the DOM as markup instead of text. An attacker who controls the Grid language configuration can provide elements with event handlers, which execute in the hosting page origin when pagination controls render. Exploitation requires pagination to be enabled but does not require additional user interaction. This issue is fixed in 3.2.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@highcharts/grid-proto a version that resolves this vulnerability.Fixed in 3.2.0 - Upgrade
Upgrade
npm/@highcharts/grid-liteto 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
After loading Highcharts Grid and before creating any grid, escape the pagination language strings in pagination.lang.pageInfo and pagination.lang.pageSizeLabel by replacing '<' with '<'.
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Highcharts Grid versions from 2.0.0 up to, but not including, 3.2.0 are affected when pagination is enabled. Deployments that do not enable pagination do not meet the stated exploitation condition.
What level of attacker control is required?
An attacker must be able to control Grid language configuration values used for pagination. No additional user interaction is required once the pagination controls render.
What can be done if an immediate upgrade is not possible?
Disable pagination to remove the stated condition required for exploitation, and ensure untrusted parties cannot control Grid language configuration strings. Upgrade to Highcharts Grid 3.2.0 when possible.