Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

Highcharts Dashboards: __proto__ data table id writes sync listeners to Object.prototype

CVE-2026-118243GHSA-jqgh-w3cc-7jqw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@highcharts/dashboards 4.2.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:L/SI:L/SA:L · score source
EPSS
  • CVE-2026-118243: 0.35% estimated exploitation activity in the next 30 days; percentile 28.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-jqgh-w3cc-7jqw

  2. Revision 1 · created ·

    Published from ghsa record GHSA-jqgh-w3cc-7jqw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-118243

Advisory: Highcharts Dashboards: `__proto__` data table id writes sync listeners to `Object.prototype`
IDs: CVE-2026-118243, GHSA-jqgh-w3cc-7jqw
Record: https://patchnext.com/advisories/cve-2026-118243 (revision 2, source checked 29 Oct 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @highcharts/dashboards 4.2.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @highcharts/dashboards: affected >= 1.0.0, < 4.2.2; fixed in 4.2.2

## Suggested inspection (read-only)
- `npm ls @highcharts/dashboards --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @highcharts/dashboards.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jqgh-w3cc-7jqw (GitHub-reviewed advisory GHSA-jqgh-w3cc-7jqw lists affected ranges: npm @highcharts/dashboards >=1.0.0 <=4.2.1)
- Verified: https://osv.dev/vulnerability/GHSA-jqgh-w3cc-7jqw (OSV record GHSA-jqgh-w3cc-7jqw lists affected ranges: npm @highcharts/dashboards >=1.0.0 <4.2.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…