@highcharts/dashboards: Highcharts Dashboards: `__proto__` data table id writes sync listeners to `Object.prototype`
What fixes it
- 4.2.2@highcharts/dashboards, npmGitHub
npm install @highcharts/dashboards@4.2.2
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
Impact
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.
Workarounds
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.apply(this,arguments)})}),'__proto__'!==new t.DataTable({id:'__proto__'}).id||Object.getOwnPropertyDescriptor(r,'id')||Object.defineProperty(r,'id',{configurable:!0,enumerable:!0,get:function(){return this.safeTableId},set:function(e){'__proto__'!==e&&'constructor'!==e||(e=t.uniqueKey(),this.autoId=!0),this.safeTableId=e}}))}}(Dashboards);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/dashboards@4.2.2. 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.
Text from GitHub Advisory Database
Affected versions 3
- @highcharts/dashboards, npm>= 1.0.0, <= 4.2.1GitHub
- highchartsaffected: >= 1.0.0, < 4.2.2CVE List
- @highcharts/dashboards, npmfrom 1.0.0, fixed in 4.2.2OSV
References 5
- github.com/highcharts/highcharts/commit/ade5a41a700212f09133223ca990a3737d1d9ec6Fixvia CVE List
- github.com/highcharts/highcharts/releases/tag/dashboards-v4.2.2Fixvia CVE List
- github.com/highcharts/highcharts/security/advisories/GHSA-jqgh-w3cc-7jqwAdvisoryvia CVE List
- github.com/advisories/GHSA-jqgh-w3cc-7jqwAdvisoryvia GitHub
- nvd.nist.gov/vuln/detail/CVE-2026-118243Referencevia GitHub