CVE-2026-118250: Highcharts: dotted series.keys paths write to Object.prototype
Impact A dot-separated key path taken from series.keys is followed without filtering the individual segments. An attacker who controls series.keys and the matching point data can use a path such as proto.polluted to set arbitrary properties on Object.prototype. The resulting properties are visible to all JavaScript running in the page, not only to the chart.
Published Oct 28, 2026
Affected packages
highcharts
- Ecosystem
- npm
- Affected
- >= 12.0.0, < 12.6.1
- Fixed in
- 12.6.1
- Check
npm ls highcharts
highcharts
- Ecosystem
- npm
- Affected
- >= 13.0.0, <= 13.0.2
- Fixed in
- 13.1.0
- Check
npm ls highcharts
highcharts
- Ecosystem
- npm
- Affected
- >= 6.1.0, < 11.4.9
- Fixed in
- 11.4.9
- Check
npm ls highcharts
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A dot-separated key path taken from series.keys is followed without filtering the individual segments. An attacker who controls series.keys and the matching point data can use a path such as __proto__.polluted to set arbitrary properties on Object.prototype. The resulting properties are visible to all JavaScript running in the page, not only to the chart. No user interaction is required beyond rendering the chart.
The injected properties are inert until other code on the page reads them, so consequences depend on the consuming application.
Workarounds
Drop-in fix - for any versions affected (6.1.0-13.0.2). Add the below IIFE to run after Highcharts is loaded.
((H)=>{const X = H.isObject;H.Point.prototype.setNestedProperty = function setNestedProperty(t,e,i){let s=i.split(".");return s.some(t=>"__proto__"===t||"constructor"===t)||s.reduce(function(t,i,s,o){let r=o.length-1===s;return t[i]=r?e:X(t[i],!0)?t[i]:{},t[i]},t),t};})(Highcharts);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 [email protected]. If you load Highcharts from the CDN, use the versioned URLs on code.highcharts.com, for example https://code.highcharts.com/13.1.1/highcharts.js. For more on each installation method, see the installation guide.
References
- https://github.com/highcharts/highcharts/security/advisories/GHSA-rmqc-xvr3-v46c
- https://nvd.nist.gov/vuln/detail/CVE-2026-118250
- https://github.com/highcharts/highcharts/pull/25313
- https://github.com/highcharts/highcharts/commit/fd4ee8140732618bbe71295aba55398fb1f8fa9e
- https://github.com/highcharts/highcharts/releases/tag/v13.1.0
- https://github.com/advisories/GHSA-rmqc-xvr3-v46c
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. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-116796
Highcharts Core: `javascript:` URL in an `xlink:href` attribute survives text filtering and reaches exported charts
high7.2Oct 28, 2026CVE-2026-118244
Highcharts Core: HTML text parsing falls back to unfiltered `innerHTML` during printing
high7.2Oct 28, 2026CVE-2026-118246
Highcharts Core: `breadcrumbs.style` keys become SVG event-handler attributes
high8.4Oct 28, 2026CVE-2026-118249
Highcharts: series column construction writes to Object.prototype
high7.1Oct 28, 2026CVE-2026-118251
Highcharts: `javascript:` URL in credits.href runs script on click
high8.4Oct 28, 2026
