Live › vulnerability › CVE-2026-118243
Go to dashboardHighcharts Dashboards stores sync listener state in plain objects keyed by DataTable ID, so a table ID of __proto__ supplied through dataPool configuration writes an enumerable property onto Object.prototype. The polluted property is visible on every object and can make lasting sync states throw, breaking features such as extremes synchronization.
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.
Teams that run Highcharts Dashboards from version 1.0.0 through 4.2.1 with component sync enabled and that load dashboard configuration which can be influenced by untrusted parties, such as user-supplied or externally stored board definitions. Boards built only from trusted, developer-authored configuration with sync off are unlikely to be exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @highcharts/dashboards | npm | >= 1.0.0, <= 4.2.1 | 4.2.2 |
npm ls highcharts or the version in the loaded highcharts.js header; versions from 1.0.0 up to but not including 4.2.2 are affected.dataPool connectors whose table IDs come from untrusted input.4.2.2.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The data cursor keeps its listener and state bookkeeping in plain objects keyed by data table id, so a table id of __proto__ supplied in the dataPool connector configuration resolves to Object.prototype when a sync registers its listeners, and the registration creates a property on Object.prototype named after the sync state and holding the internal listener array. The property name begins with a state prefix fixed by the library, to which the sync group option can append an attacker-chosen suffix, and its value is the library's own listener array, but the property is enumerable and visible on every object in the page, and emitting a lasting state for that table id then throws, so syncs that keep lasting states, such as extremes, stop working. Exploitation requires that untrusted data reach the Dashboards configuration and that a sync such as highlight or extremes be enabled on a component using that table, which the same configuration can do. No user interaction is required beyond loading the board.
The injected property is inert until other code on the page reads or enumerates it, so consequences depend on the consuming application.
Drop-in fix - for any Highcharts Dashboards versions affected (1.0.0-4.2.1). Add the below IIFE to run after Highcharts Dashboards is loaded.
!function(t){if(t&&t.DataCursor&&t.DataTable){var e=t.DataCursor.prototype,r=t.DataTable.prototype;e.tableIdPollutionPatched||(e.tableIdPollutionPatched=!0,null!==Object.getPrototypeOf((new t.DataCursor).listenerMap)&&['addListener','emitCursor','remitCursor','removeListener'].forEach(function(t){var r=e[t];r&&(e[t]=function(){var t;return t=this,['listenerMap','stateMap'].forEach(function(e){var r,a=t[e];a&&null!==Object.getPrototypeOf(a)&&(r=Object.create(null),Object.keys(a).forEach(function(t){r[t]=a[t]}),t[e]=r)}),r.(,)})}),!== t.({:}).||.(r,)||.(r,,{:!,:!,:(){ .},:(){!==e&&!==e||(e=t.(),.=!),.=e}}))}}();
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/[email protected]. If you load Highcharts Dashboards from a CDN, use a versioned URL, for example https://code.highcharts.com/dashboards/4.2.2/dashboards.js. For more on each installation method, see the installation guide.
This page as .md · .json · in your agent: get_signal("CVE-2026-118243")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.