Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Highcharts: series column construction writes to Object.prototype

CVE-2026-118249GHSA-gfvx-2c2g-38wq

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (highcharts 13.1.0), 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

  • npm highcharts

    Affected
    >= 13.0.0, < 13.1.0
    Fixed in
    13.1.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:L/SI:L/SA:L · score source
EPSS
  • CVE-2026-118249: 0.36% estimated exploitation activity in the next 30 days; percentile 30.20 (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 When series columns are built from point objects, the point option keys are used directly as data column ids, so the write that populates a column reaches `Object.prototype` and the `Object` constructor. Keys named `proto` and `constructor` survive `JSON.parse` as own enumerable properties, so an attacker who controls the point objects can set integer-keyed properties on `Object.prototype`, one per point index, to values of their choosing. Named properties cannot be reached this way. The integer keys still affect every object in the page: reading an out-of-range index on any array or plain object returns the attacker's value, and `for...in` over any object yields the injected keys, so unrelated code can take branches it should not using attacker-supplied data, and rendering can fail as a side effect. The properties remain in place once the chart has been built, and no user interaction is required beyond rendering the chart. Consequences beyond disruption depend on the…

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

    Amended from osv record GHSA-gfvx-2c2g-38wq

  2. Revision 1 · created ·

    Published from ghsa record GHSA-gfvx-2c2g-38wq

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-118249

Advisory: Highcharts: series column construction writes to Object.prototype
IDs: CVE-2026-118249, GHSA-gfvx-2c2g-38wq
Record: https://patchnext.com/advisories/cve-2026-118249 (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: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: highcharts 13.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm highcharts: affected >= 13.0.0, < 13.1.0; fixed in 13.1.0

## Suggested inspection (read-only)
- `npm ls highcharts --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.
- 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-gfvx-2c2g-38wq (GitHub-reviewed advisory GHSA-gfvx-2c2g-38wq lists affected ranges: npm highcharts >=13.0.0 <=13.0.2)
- Verified: https://osv.dev/vulnerability/GHSA-gfvx-2c2g-38wq (OSV record GHSA-gfvx-2c2g-38wq lists affected ranges: npm highcharts >=13.0.0 <13.1.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…