Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-65hg-cf3f-5m39

Highcharts Core: HTML text parsing falls back to unfiltered `innerHTML` during printing

CVSS 7.2 HighEPSS 0.0034 · 27th percentile

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

PackageEcosystemAffectedFixed in
highchartsnpm>=12.0.0, <12.6.1 || >=13.0.0, <13.1.012.6.1, 13.1.0
Identifiers
GHSA-65hg-cf3f-5m39 · CVE-2026-118244
Weakness (CWE)
CWE-79
Tags
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 versions 12.0.0 up to 12.6.1 and 13.0.0 up to 13.1.0 are affected by an HTML text parsing fallback that inserts unfiltered markup into the page. When the hosting page re-renders the chart from a beforeprint handler in Chromium, HTML-rendered text options such as titles, labels and responsive-rule text can carry event handlers that run in the host page's origin, and printing from the exporting menu triggers this. The fix is to upgrade to version 12.6.1 or 13.1.0, or to apply the workaround given in the source for other affected versions.

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
7.2 High 4.0 CVSS:4.0/AV:N/AC:L/AT:P/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. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 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.