Highcharts Dashboards: `__proto__` data table id writes sync listeners to `Object.prototype`
Impact
Highcharts Dashboards versions 1.0.0 to 4.2.1 are affected by a prototype pollution vulnerability, where an attacker can modify Object.prototype by supplying a specific table id, potentially causing issues with sync functionality. Exploitation requires untrusted data to reach the Dashboards configuration. The impact depends on the consuming application.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.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.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 1.0.0 before 4.2.2Semantic versions | 4.2.2 |
Version evidence: OSV · GHSA-jqgh-w3cc-7jqw
View original version evidence (0 explicit versions)
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
highcharts · GitHub_M
highcharts
1 range
highcharts · GitHub_M
highcharts
Compare with this publisher’s ranges. This does not inspect your installation.
affected
>= 1.0.0, < 4.2.2
Other versions: unknown
Original source 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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-118243View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
GitHub_M
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.