CVE-2026-85061: MapLibre GL JS: XSS Sanitizer Bypass in DOM.sanitize() via Live NamedNodeMap Removal Skip
MapLibre GL JS is an interactive vector tile map library for web browsers. Prior to 6.4.1, DOM.sanitize() in src/util/dom.ts iterates elem.attributes as a live NamedNodeMap while removeAttributes() removes attributes from the same collection, shifting indexes and skipping an adjacent dangerous attribute. An attacker who controls untrusted third-party style attribution strings or user-supplied custom attributions can supply consecutive dangerous attributes, causing an attribute such as onload or ontoggle to survive sanitization and execute when the attribution control inserts the content into innerHTML. A victim must render the affected map content for the script to execute. This issue is fixed in version 6.4.1.
Security readout for executives and security teams
Plain-English summary
MapLibre GL JS before 6.4.1 can fail to remove malicious HTML attributes from map attribution text. If an application renders attacker-controlled attribution, browser script can execute in the application’s security context, potentially exposing data or enabling unauthorized actions.
Executive priority
Treat internet-facing applications that render externally controlled attribution as an urgent remediation priority. Upgrade promptly and confirm the production bundle changed. Less-exposed deployments should remain prioritized because the vulnerable sanitizer is a client-side trust boundary and the reported impact is critical.
Technical view
DOM.sanitize() iterates a live NamedNodeMap while deleting attributes. Deletion shifts the collection, so an adjacent dangerous attribute can escape inspection. When attribution content is subsequently assigned through innerHTML, a surviving event-handler attribute such as onload or ontoggle may execute. Version 6.4.1 fixes the flaw.
Likely exposure
Exposure is limited to applications using MapLibre GL JS versions earlier than 6.4.1 that render untrusted third-party style attribution or user-supplied custom attribution. Applications without attacker influence over attribution content have lower practical exposure, but bundled and transitive copies should still be inventoried.
Exploitation context
The supplied sources describe network-reachable, low-complexity XSS without privileges or a separate user action beyond rendering affected map content. The CVSS 3.1 score is 10.0. This CVE is not listed as KEV in the bundle, and no supplied source establishes active exploitation.
Researcher notes
Validation should focus on the mutation-during-iteration defect and the attribution-to-innerHTML data path. Consecutive removable attributes are the key sanitizer edge case. Avoid treating library presence alone as proven exploitability; confirm attacker control of attribution and rendering by a victim. The supplied evidence does not establish exploitation in the wild.
Mitigation direction
Upgrade MapLibre GL JS to version 6.4.1 or later.
Identify and update bundled or transitive copies below version 6.4.1.
Until upgraded, prevent untrusted parties from controlling style or custom attribution strings.
Apply defense-in-depth browser policies according to existing application security guidance.
Validation and detection
Confirm deployed MapLibre GL JS versions through manifests, lockfiles, bundles, and runtime asset inspection.
Trace whether third-party styles or users can influence attribution content.
Verify production assets resolve to version 6.4.1 or later after deployment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.