What is CVE-2026-85061?

CVE-2026-85061 is a critical-severity cross-site scripting (XSS) vulnerability in maplibre-gl (npm), affecting versions <= 6.4.0. It is fixed in 6.4.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2026-85061?

CVE-2026-85061 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of maplibre-gl are affected by CVE-2026-85061?

maplibre-gl (npm) versions <= 6.4.0 is affected.

Is there a fix for CVE-2026-85061?

Yes. CVE-2026-85061 is fixed in 6.4.1. Upgrade to this version or later.

Is CVE-2026-85061 exploitable, and should I be worried?

Whether CVE-2026-85061 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-85061 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-85061?

Upgrade maplibre-gl to 6.4.1 or later.

CVE-2026-85061 in maplibre-gl

Q: How severe is CVE-2026-85061?

CVE-2026-85061 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of maplibre-gl are affected by CVE-2026-85061?

maplibre-gl (npm) versions <= 6.4.0 is affected.

Q: Is there a fix for CVE-2026-85061?

Yes. CVE-2026-85061 is fixed in 6.4.1. Upgrade to this version or later.

Q: Is CVE-2026-85061 exploitable, and should I be worried?

Whether CVE-2026-85061 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-85061 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-85061?

Upgrade maplibre-gl to 6.4.1 or later.

Summary

MapLibre GL JS: XSS Sanitizer Bypass in DOM.sanitize() via Live NamedNodeMap Removal Skip

Workarounds

Sanitizing the attribute field of a source before passing it down to maplibre

Impact

DOM.sanitize() in src/util/dom.ts iterated elem.attributes (a live NamedNodeMap) while calling elem.removeAttribute() in the same loop. Removing an attribute shifts subsequent attributes down by one index, causing the iterator to skip the adjacent attribute.

An attacker can provide an HTML payload with consecutive dangerous attributes (such as <details open onload="1" ontoggle="...">). The first attribute is stripped while the second survives and executes upon insertion into innerHTML via the attribution control without requiring user interaction (zero-click XSS).

Applications rendering untrusted/third-party style attribution strings or user-supplied custom attributions are impacted.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2026-85061 has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.4.1); upgrading removes the vulnerable code path.

Affected versions

maplibre-gl (<= 6.4.0)

Security releases

maplibre-gl → 6.4.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue has been resolved by creating a static snapshot of attributes using Array.from(elem.attributes) before iteration. Please upgrade to maplibre-gl version 6.4.1 (or latest).

Frequently Asked Questions

What is CVE-2026-85061? CVE-2026-85061 is a critical-severity cross-site scripting (XSS) vulnerability in maplibre-gl (npm), affecting versions <= 6.4.0. It is fixed in 6.4.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2026-85061? CVE-2026-85061 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of maplibre-gl are affected by CVE-2026-85061? maplibre-gl (npm) versions <= 6.4.0 is affected.
Is there a fix for CVE-2026-85061? Yes. CVE-2026-85061 is fixed in 6.4.1. Upgrade to this version or later.
Is CVE-2026-85061 exploitable, and should I be worried? Whether CVE-2026-85061 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-85061 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-85061? Upgrade maplibre-gl to 6.4.1 or later.