CVE-2026-118243: Highcharts Dashboards: `__proto__` data table id writes sync listeners to `Object.prototype`

Published Oct 28, 2026
·
Updated

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);

Live demo & testing

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.

Other sources

Highcharts JS is a JavaScript charting library based on SVG. From 1.0.0 until 4.2.2, Highcharts Dashboards stores DataCursor listener and state maps in plain objects keyed by DataTable ID. A proto table ID supplied through dataPool connector configuration resolves to Object.prototype, and sync registration creates an enumerable property there whose suffix can be influenced through the sync group option. The property is visible on every object, and lasting sync states can throw and stop features such as extremes synchronization. Exploitation requires untrusted dashboard configuration and an enabled component sync, but no user interaction beyond loading the board. This issue is fixed in 4.2.2.

— MITRE

Affected Software

3 affected componentsFixes available
Highcharts Highcharts Dashboards>=1.0.0<4.2.2
npm/@highcharts/dashboards>=1.0.0<=4.2.1
4.2.2
npm/@highcharts/dashboards>=1.0.0<4.2.2
4.2.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@highcharts/dashboards to a version that resolves this vulnerability.

    Fixed in 4.2.2
  2. Upgrade

    Upgrade @highcharts/dashboards to a version that resolves this vulnerability.

    Fixed in 4.2.2
  3. Compensating control

    Add the provided drop-in IIFE after Highcharts Dashboards is loaded to patch affected versions 1.0.0-4.2.1.

Event History

Oct 28, 2026
CVE Published
via MITRE·05:33 PM
Data Sourced
via MITRE·05:33 PM
DescriptionWeakness
Data Sourced
via OSV·05:33 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·07:55 PM
Data Sourced
via GitHub·07:55 PM
DescriptionWeaknessAffected Software
Data Sourced
via OSV·07:55 PM
Affected Software

Frequently Asked Questions

1

Which deployments are realistically exposed?

Deployments using Highcharts Dashboards versions from 1.0.0 through 4.2.1 are exposed when they load untrusted dashboard configuration, allow a DataTable ID of __proto__ through dataPool connector configuration, and have component synchronization enabled.

2

What does an attacker need to exploit this issue?

An attacker needs the ability to supply dashboard configuration that reaches the dataPool connector configuration. They also need component sync to be enabled; no additional user interaction is required after the board loads.

3

Are default deployments affected?

The issue is not described as affecting every default deployment. Exploitation depends on both untrusted dashboard configuration and enabled component sync.

4

What can be done if upgrading is not immediately possible?

Do not accept untrusted dashboard configuration, and prevent DataTable IDs from being set to __proto__ through dataPool connector configuration. Disable component synchronization where it is not required.

5

How can I determine whether an instance may have been affected?

Check whether a loaded dashboard used a __proto__ DataTable ID and enabled synchronization. A successful exploit creates an enumerable property on Object.prototype, with a property-name suffix influenced by the sync group option; persistent sync-state errors may also stop features such as extremes synchronization.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203