Advisory record · GHSA-35rr-xwfh-x789

Highcharts Core: `breadcrumbs.style` keys become SVG event-handler attributes

CVSS 8.4 HighEPSS 0.0034 · 27th percentile

Published by the GitHub Advisory Database at 28 Oct 2026, 19:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
highchartsnpm>=10.0.0, <11.4.9 || >=12.0.0, <12.6.1 || >=13.0.0, <13.1.011.4.9, 12.6.1, 13.1.0
Identifiers
GHSA-35rr-xwfh-x789 · CVE-2026-118246
Weakness (CWE)
CWE-79
Published
28 Oct 2026
Updated
28 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Highcharts (npm package highcharts) versions 10.0.0 up to 11.4.9, 12.0.0 up to 12.6.1, and 13.0.0 up to 13.1.0 are vulnerable. In these versions, keys supplied through the breadcrumbs style option are applied as unfiltered SVG attributes, so keys naming event handlers become live handlers on the breadcrumb button. An attacker who can control the chart configuration can get script to run in the hosting page's origin once a user drills down and interacts with the breadcrumbs. Upgrade to 11.4.9, 12.6.1, or 13.1.0, depending on the release line in use.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 28 Oct 2026, 17:47 UTC Confirmed by the CVE List
  2. 28 Oct 2026, 18:17 UTC Confirmed by NVD
  3. 31 Oct 2026, 13:33 UTC First seen by agentprime
  4. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.