CVE-2026-118244: Highcharts Core: HTML text parsing falls back to unfiltered `innerHTML` during printing
Impact When the HTML text parser cannot obtain a document from DOMParser because the call throws, it falls back to assigning the raw markup to the innerHTML of an element created in the hosting document, and the allow-list is applied only to the resulting DOM afterwards. In Chromium the Trusted Types policy callback that the parser uses throws while a beforeprint handler is running, so if the hosting page re-renders the chart from a beforeprint handler, every HTML-rendered text option parsed at that moment, such as useHTML titles, axis labels and data labels or text set by responsive rules, is inserted unsanitized, and event handlers embedded in that markup run in the origin of the page hosting the chart. Exploitation requires that untrusted data reach the chart configuration, that the hosting page update the chart from a beforeprint handler in Chromium, and that printing be started, which the print item of the exporting menu does on its own. Charts built with Highcharts Stock, Maps and Gantt are included, since those ship from the same package as Core.
Workarounds Drop-in fix - for any versions affected (12.0.0-13.0.2). Add the below IIFE to run after Highcharts is loaded. ((n)=>{n.AST.prototype.parseMarkup=function parseMarkup(t){let e,i=[];t=t.trim().replace(/ style=(["'])/g," data-style=$1");try{e=new DOMParser().parseFromString(tI?tI.createHTML(t):t,"text/html")}catch{}if(!e)try{e=new DOMParser().parseFromString(t,"text/html")}catch{}e||((e=n.doc.implementation.createHTMLDocument("")).body.innerHTML=t);let s=(t,e)=>{let i=t.localName||t.nodeName.toLowerCase(),o={tagName:i};"#text"===i&&(o.textContent=t.textContent||"");let r=t.attributes;if(r){let t={};[].forEach.call(r,e=>{"data-style"===e.name?o.style=tB.parseStyle(e.value):t[e.name]=e.value}),o.attributes=t}if(t.childNodes.length){let e=[];[].forEach.call(t.childNodes,t=>{s(t,e)}),e.length&&(o.children=e)}e.push(o)};return[].forEach.call(e.body.childNodes,t=>s(t,i)),i};})(Highcharts); Live demo & testing
Obtaining the patched version The patched releases are available from all the usual distribution channels. With npm, upgrade the affected package to the patched version listed above, for example npm install highcharts@13.1.0. If you load Highcharts from the CDN, use the versioned URLs on code.highcharts.com, for example https://code.highcharts.com/13.1.0/highcharts.js. For more on each installation method, see the installation guide.
Other sources
Highcharts JS is a JavaScript charting library based on SVG. From 12.0.0 until 12.6.1 and 13.1.0, Highcharts falls back to assigning raw markup to innerHTML when DOMParser cannot return a document, before its allow-list is applied. In Chromium, the Trusted Types callback can throw while a beforeprint handler runs, so a page that redraws a chart during beforeprint can insert untrusted HTML text options into the hosting document. Event handlers in that markup then run in the page origin when printing begins. The issue affects HTML-rendered titles, labels, data labels, responsive text, and the Stock, Maps, and Gantt products shipped in the same package. This issue is fixed in 12.6.1 and 13.1.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/highchartsto a version that resolves this vulnerability.Fixed in 13.1.0 - Upgrade
Upgrade
npm/highchartsto a version that resolves this vulnerability.Fixed in 12.6.1 - Upgrade
Upgrade
highchartsto a version that resolves this vulnerability.Fixed in 12.6.1 - Upgrade
Upgrade
highchartsto a version that resolves this vulnerability.Fixed in 13.1.0 - Configuration
Add the provided IIFE after Highcharts is loaded as a workaround for affected versions 12.0.0-13.0.2.
Highcharts Core AST parser AST.prototype.parseMarkup = Use the provided drop-in IIFE implementation
Event History
Frequently Asked Questions
Who is realistically exposed to exploitation?
Applications using affected Highcharts versions that render attacker-controlled or otherwise untrusted text through HTML-rendered titles, labels, data labels, or responsive text are exposed. The same package issue also affects Highcharts Stock, Maps, and Gantt.
What conditions are needed for an attacker to trigger the issue?
The application must redraw a chart from a beforeprint handler, and Chromium must take the DOMParser fallback path because its Trusted Types callback throws. Untrusted HTML text options must be present; event handlers in that markup execute in the page origin when printing begins.
Are fixed versions available?
Yes. The issue is fixed in Highcharts 12.6.1 and 13.1.0.