CVE
geojson-vt: Uncontrolled Recursion in Nested GeoJSON GeometryCollection
Affects @maplibre/geojson-vt 6.1.0 and earlier when a GeoJSONVT instance is built from a deeply nested GeometryCollection. Fixed in 6.1.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.1.1
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Affected is maplibre geojson-vt, a JavaScript library for slicing GeoJSON into vector tiles. Remotely, without logging in, an attacker can send one crafted, deeply nested GeometryCollection that makes the library exhaust the call stack and crash the process, causing a denial of service.
Read the original description
geojson-vt is a JavaScript library for slicing GeoJSON data into vector tiles on the fly, primarily designed to enable rendering and interacting with large geospatial datasets on the browser side (without a server). Prior to version 6.1.1, @maplibre/geojson-vt contains an uncontrolled recursion vulnerability in its GeoJSON conversion logic. When a GeoJSONVT instance is constructed with a deeply nested GeometryCollection object, the mutually recursive functions featureToInternal and convertGeometryCollection in src/convert.ts exhaust the Node.js call stack, causing an unhandled RangeError: Maximum call stack size exceeded that terminates the process. Because the library is widely used in server-side tile services that accept GeoJSON over the network, a remote unauthenticated attacker can trigger a denial-of-service by sending a single crafted payload. No authentication is required, and no non-default library options are needed. This issue has been patched in version 6.1.1.
Who should check
Teams running @maplibre/geojson-vt 6.1.0 or earlier in server-side tile or GeoJSON services that accept untrusted GeoJSON input
Read the source excerpt
“@maplibre/geojson-vt v6.1.0 contains an uncontrolled recursion vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 6.1.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-58505 (geojson-vt: Uncontrolled Recursion in Nested GeoJSON GeometryCollection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-58505 (entry last updated 2026-11-11):
Affected:
- maplibre geojson-vt: fixed in 6.1.1
Fixed versions: 6.1.1.
Conditions (all must be true for the bug to be hit):
- Affected: @maplibre/geojson-vt v6.1.0 and earlier (up to 6.1.0) (source: https://github.com/maplibre/geojson-vt/security/advisories/GHSA-75qh-632x-j5pr)
- Input is a deeply nested GeometryCollection passed to the GeoJSONVT constructor (source: https://github.com/maplibre/geojson-vt/security/advisories/GHSA-75qh-632x-j5pr)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-58505 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-58505 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/maplibre/geojson-vt/security/advisories/GHSA-75qh-632x-j5pr
- https://github.com/maplibre/geojson-vt/pull/156
- https://github.com/maplibre/geojson-vt/commit/cb85688270d80894ce377969c75e631fe4b04c82
- https://github.com/maplibre/geojson-vt/releases/tag/v6.1.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-58505
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-58505"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- maplibre geojson-vt
fixed in 6.1.1
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58505
Is CVE-2026-58505 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Constructing a GeoJSONVT instance from a deeply nested GeometryCollection triggers uncontrolled recursion. The call stack overflows, and the Node.js process crashes with an unhandled RangeError (Maximum call stack size exceeded).Source: github.com
Which versions are affected by CVE-2026-58505?
geojson-vt: before 6.1.1.Source: cve.now feed data
Am I affected, and how do I check?
Versions of @maplibre/geojson-vt 6.1.0 and earlier are affected, in setups that pass deeply nested GeometryCollection objects to the GeoJSONVT constructor. To check a installed version, look at the version field in node_modules/@maplibre/geojson-vt/package.json.Source: github.com
How do I fix CVE-2026-58505?
Upgrade @maplibre/geojson-vt to 6.1.1 or later, the version the product range lists as fixed.Source: github.com