Live › vulnerability › CVE-2026-118244
Go to dashboardHighcharts falls back to raw innerHTML when DOMParser fails, and in Chromium a Trusted Types error during a beforeprint redraw lets untrusted chart text insert HTML. Event handlers in that markup then run in the page origin when printing starts.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Pages that use Highcharts in a browser and feed user-controlled or third-party text into HTML-rendered titles, labels, data labels or responsive text are exposed, and the Stock, Maps and Gantt products in the same package are included. Pages that only show fixed chart text, or that do not redraw charts during printing, are less exposed. The sources do not say whether DOMParser failure is common in practice.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| highcharts | npm | >= 12.0.0, < 12.6.1 | 12.6.1 |
| highcharts | npm | >= 13.0.0, <= 13.0.2 | 13.1.0 |
npm ls highcharts or by reading node_modules/highcharts/package.json, and look for versions from 12.0.0 through 12.6.1 or 13.0.0 through 13.1.0beforeprint handler that redraws charts and renders untrusted text in titles, labels or data labels12.6.1 or 13.1.0beforeprint handlersEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
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);
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 [email protected]. 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118244")
NVD data is provided by NIST and is public domain · GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.