Live › vulnerability › CVE-2026-118249
Go to dashboardHighcharts JS builds series data columns using point option keys directly as IDs, so crafted __proto__ or constructor keys in parsed chart data can write to Object.prototype. The polluted values then affect reads and for-in loops across the page, disrupting rendering or application logic when a chart is rendered.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Applications that use Highcharts 13.0.0 through 13.1.x to render charts from data parsed from untrusted or external sources are exposed, because the crafted point keys come from that data. Teams on versions before 13.0.0 or on 13.1.0 and later, or who only chart their own fixed data, can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| highcharts | npm | >= 13.0.0, <= 13.0.2 | 13.1.0 |
npm ls highcharts or inspect the lockfile to find the installed Highcharts version.from 'highcharts' or require('highcharts') to confirm the library is used in a page that renders chart data from parsed input.13.1.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
When series columns are built from point objects, the point option keys are used directly as data column ids, so the write that populates a column reaches Object.prototype and the Object constructor. Keys named __proto__ and constructor survive JSON.parse as own enumerable properties, so an attacker who controls the point objects can set integer-keyed properties on Object.prototype, one per point index, to values of their choosing. Named properties cannot be reached this way. The integer keys still affect every object in the page: reading an out-of-range index on any array or plain object returns the attacker's value, and for...in over any object yields the injected keys, so unrelated code can take branches it should not using attacker-supplied data, and rendering can fail as a side effect. The properties remain in place once the chart has been built, and no user interaction is required beyond rendering the chart.
Consequences beyond disruption depend on the consuming application.
Drop-in fix - for any versions affected (6.1.0-13.0.2). Add the below IIFE to run after Highcharts is loaded.
;!function(t){if(t&&t.Point&&!t.Point.prototype.protoPollutionPatched){var o=t.Point.prototype,r=o.optionsToObject,e=o.setNestedProperty,n=Object.prototype.hasOwnProperty;o.optionsToObject=function(t){if(t&&"object"==typeof t&&!Array.isArray(t)&&(n.call(t,"__proto__")||n.call(t,"constructor"))){var o={};for(var e in t)n.call(t,e)&&!c(e)&&(o[e]=t[e]);t=o}return r.call(this,t)},o.setNestedProperty=function(t,o,r){return String(r).split(".").some(c)?t:e.call(this,t,o,r)},o.protoPollutionPatched=!0}function c(t){return"__proto__"===t||"constructor"===t}}(Highcharts);
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.0/highcharts.js. For more on each installation method, see the installation guide.
This page as .md · .json · in your agent: get_signal("CVE-2026-118249")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.