GHSA-r5wg-q8fc-p6w2 - 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](https://www.highcharts.com/docs/grid/installation).
HIGH
Severity & confidence
Source severityhigh
Platform severityhigh
Confidencehigh
Exploitationunknown
CVSS-
Affected
Vendors@highcharts
Products@highcharts/grid-lite@highcharts/grid-pro
Reporting sources (2)
GitHub Security Advisories
NIST NVD - National Vulnerability Database
Timeline & provenance
Published2026-10-28T19:57:34
Last updated2026-10-31T19:07:17
Ingested2026-10-28T19:58:58
FreshnessNEAR-REAL-TIME
Threat typeadvisory
Recommended action
Review the advisory and upgrade affected packages to the first patched version.
Next steps
- Identify affected systems in your environment.
- Apply the vendor patch or mitigation guidance.
- Review logs for indicators described in the advisory.
- Follow the affected vendor/product to track updates.
Confidence explanation
Reported by a government or cert-grade source (CISA, NCSC, NVD, ENISA, MSRC).
Source type: vendor ยท Original: GitHub Security Advisories