Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

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

CVE-2026-85061GHSA-jrc7-96c5-q579

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (maplibre-gl 6.4.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-85061: 0.52% estimated exploitation activity in the next 30 days; percentile 44.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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. Patches 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). Workarounds Sanitizing the attribute field of a source before passing it down to maplibre

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jrc7-96c5-q579

  2. Revision 2 · amended ·

    Amended from osv record GHSA-jrc7-96c5-q579

  3. Revision 1 · created ·

    Published from ghsa record GHSA-jrc7-96c5-q579

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-85061

Advisory: MapLibre GL JS: XSS Sanitizer Bypass in DOM.sanitize() via Live NamedNodeMap Removal Skip
IDs: CVE-2026-85061, GHSA-jrc7-96c5-q579
Record: https://patchnext.com/advisories/cve-2026-85061 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: maplibre-gl 6.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm maplibre-gl: affected <= 6.4.0; fixed in 6.4.1

## Suggested inspection (read-only)
- `npm ls maplibre-gl --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on maplibre-gl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jrc7-96c5-q579 (GitHub-reviewed advisory GHSA-jrc7-96c5-q579 lists affected ranges: npm maplibre-gl >=0 <=6.4.0)
- Verified: https://osv.dev/vulnerability/GHSA-jrc7-96c5-q579 (OSV record GHSA-jrc7-96c5-q579 lists affected ranges: npm maplibre-gl >=0 <6.4.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…