Highcharts vulnerabilitiesHighcharts: known vulnerabilities and safe versions
npm: highcharts
Highcharts has 3 known vulnerability records: 2 in the npm advisory data (GitHub Advisory Database via OSV, the same source npm audit uses) and 1 only in Retire.js (CDN builds and advisories without a CVE).
By branch: 9.x has no known records; 8.x has no fixed release in the records; 7.x has no fixed release in the records; 6.x has no fixed release in the records.
Vulnerabilities and safe version by branch
Safe version: on that branch, this release and every later one (up to the branch's latest release, where known) fall outside every known record's range. Candidates are only the records' own fixed versions and the branch's latest release; "No fix" means moving off the branch.
| Branch | Support | Latest on branch | Records | Safe version |
|---|---|---|---|---|
| 9.x | — | — | 0 | — |
| 8.x | — | — | 2high | No fix |
| 7.x | — | — | 2high | No fix |
| 6.x | — | — | 3high | No fix |
Support dates appear only for libraries that endoflife.date tracks.
Records
Newest first. Ranges are the record's own data; several ranges mean separate fixes per branch.
CVE-2021-294892021-05-05
Options structure open to XSS if passed unfiltered
Affected versions: < 9.0.0
medium 5.4
Fixed in: 9.0.0
CVE-2018-208012019-03-14
In js/parts/SvgRenderer.js in Highcharts JS before 6.1.0, the use of backtracking regular expressions permitted an attacker to conduct a den
Affected versions: < 6.1.0
high 7.5
Fixed in: 6.1.0
EPSS 3.1%
Versions of `highcharts` prior to 7.2.2 or 8.1.1 are vulnerable to Cross-Site Scripting (XSS)
Affected versions: < 7.2.2 · >= 8.0.0, < 8.1.1
high
Fixed in: 7.2.2, 8.1.1
Sources and method
Ranges: GitHub Advisory Database (OSV npm export, daily) and Retire.js (Apache-2.0). Exploitation: CISA KEV, FIRST EPSS and exploit maturity from the Noroxi CVE database. Support dates: endoflife.date.
This page and the JavaScript library scan use the same matching rule: a row without bounds is not evidence, and versions are compared in one place. A record without a version range never counts as "affected" in the version check.
Data as of October 22, 2026.