Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55178 high CVSS 7.5

Information Disclosure in @geolens/sdk (CVE-2026-55178)

Summary

Vulnerability in @geolens/sdk (CVE-2026-55178). Confidential information can be exposed externally. Exploitable via GET /maps/{id}. Mitigation: upgrade to 1.2.3 or later.

Original description

The description as published by the source.

Summary

Multiple GeoLens read/link endpoints authorized only the resource named in the
request URL (a map, a VRT, a source dataset, an AI request) and failed to
re-authorize a second, caller-influenced dataset that the request reached
through a relationship, layer reference, mosaic source, or request body. This
"authorize the URL resource, read a different dataset un-re-authorized"
pattern let callers read data from datasets they have no access to.

The most severe instances require no authentication at all (anonymous,
network-only). Others require only the default editor role that any
self-service signup / upload user receives.

All issues are fixed in 1.2.3. There is no complete configuration
workaround — upgrading is the only full remediation.

Impact

Depending on the endpoint, an attacker can read, for datasets they cannot
otherwise access:

  • the dataset's vector tile data (actual feature geometries/attributes),
  • the dataset's raster pixels,
  • backing-table rows,
  • and metadata — table name, column schema, feature count, extent, source
    URL/filename, contacts, and sampled row values.

Affected versions

All versions prior to 1.2.3 (includes the published 1.0.0, 1.2.0, and
1.2.2 releases and their PyPI/npm/GHCR artifacts). Fixed in 1.2.3.

Findings

1. Anonymous metadata + private vector-tile disclosure via public maps (PR #235)
GET /maps/{id} and GET /maps/{id}/style.json authorized the map but n…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55178 has been found in @geolens/sdk.
Attackers can target a specific entry point like GET /maps/{id} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade @geolens/sdk to 1.2.3 or later.
If unsure, ask your IT team or search "@geolens/sdk CVE-2026-55178" on the vendor's site.

CVE-2026-55178 (@geolens/sdk) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /maps/{id} / GET /maps/{id}/style.json / GET /collections/datasets/items / POST /ai/metadata/{summary
Patched: 1.2.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in @geolens/sdk. Attackers reach the vulnerable code path via GET /maps/{id} without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @geolens/sdk. Attack surface: GET /maps/{id} / GET /maps/{id}/style.json / GET /collections/datasets/items / POST /ai/metadata/{summary.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.2.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /maps/{id} requests with malformed payloads or SQL meta-characters. Run grep -r '@geolens/sdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@geolens/sdk' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @geolens/sdk を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /maps/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /maps/{id} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @geolens/sdk to 1.2.3

    ステージング環境で 1.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /maps/{id} on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @geolens/sdk
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.2.3"}]}]
pip geolens-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.3"}]}]
pip geolens
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.3"}]}]
PyPI geolens-cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.3"}]}]
PyPI geolens
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details