GeoLens is a self-hosted geospatial data catalog with semantic search, OGC and STAC APIs, and a map builder. Prior to 1.2.3, multiple read and link endpoints authorize only the resource named in the request URL and fail to re-authorize a second caller-influenced dataset reached through a relationship, map layer, VRT source, externalId lookup, or request body. When a public map references a private dataset, anonymous callers can use GET /maps/{id} and GET /maps/{id}/style.json to obtain the private layer's metadata, sampled values, or vector tiles. The style response can expose a replayable HMAC tile URL that is bound to neither a user nor a map. When a public source dataset has a relationship to a private target dataset, anonymous callers can use the dataset relationship APIs to enumerate the relationship and read rows from the private target's backing table. Anonymous callers can also use GET /collections/datasets/items with an externalId dataset UUID to obtain metadata for any private, restricted, or unpublished dataset because that lookup performs no visibility check. Authenticated users with the default editor role can mosaic another user's private raster into an owned VRT and read its pixels, and POST /ai/metadata/{summary,keywords,lineage,quality-statement} accepts a body-controlled dataset_id without a visibility check and returns private metadata and sample values. Pre-existing vrt_source_links also expose unauthorized member metadata and health unless each member is filtered at read time. These paths can disclose vector geometries and attributes, raster pixels, table rows, table names, column schemas, feature counts, extents, source URLs and filenames, contacts, and sampled row values. This issue is fixed in version 1.2.3.
CVE-2026-55178
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
September 17, 2026
Advisory Details (10)
Auto-updated Sep 15, 2026commit 31a103b96b9f (geolens-io/geolens)
Fix landed in geolens-io/geolens commit 31a103b96b9f — awaiting tagged release
https://github.com/geolens-io/geolens/commit/31a103b96b9fd6ad90308b3e27a581852c4a69bdcommit 2c031da8e753 (geolens-io/geolens)
Fix landed in geolens-io/geolens commit 2c031da8e753 — awaiting tagged release
https://github.com/geolens-io/geolens/commit/2c031da8e753639ff0e36d47ca05bbb96fbe4a9ecommit 07dfb1c63ecf (geolens-io/geolens)
Fix landed in geolens-io/geolens commit 07dfb1c63ecf — awaiting tagged release
https://github.com/geolens-io/geolens/commit/07dfb1c63ecfc065c0c47b7718ec6ebe97798b1ecommit 01bc87da03a5 (geolens-io/geolens)
Fix landed in geolens-io/geolens commit 01bc87da03a5 — awaiting tagged release
https://github.com/geolens-io/geolens/commit/01bc87da03a5ecd0322c42388f4bfced7cb2ed06fix(ai): authorize the requested dataset on AI metadata endpoints (SEC-D)
Fix merged in geolens-io/geolens PR #238 on 2026-06-10 — awaiting tagged release
https://github.com/geolens-io/geolens/pull/238fix(vrt): authorize VRT source datasets at link time + filter unauthorized members on read (SEC-C/SEC-E)
Fix merged in geolens-io/geolens PR #237 on 2026-06-10 — awaiting tagged release
https://github.com/geolens-io/geolens/pull/237fix(ogc): enforce dataset visibility on the externalId OGC item lookup (SEC-B)
Fix merged in geolens-io/geolens PR #236 on 2026-06-10 — awaiting tagged release
https://github.com/geolens-io/geolens/pull/236fix(maps): re-authorize each layer's dataset on anonymous map read endpoints (SEC-A)
Fix merged in geolens-io/geolens PR #235 on 2026-06-10 — awaiting tagged release
https://github.com/geolens-io/geolens/pull/235fix(catalog): authorize relationship targets in related-record endpoints
Fix merged in geolens-io/geolens PR #234 on 2026-06-10 — awaiting tagged release
https://github.com/geolens-io/geolens/pull/234Cross-dataset authorization bypass discloses private dataset metadata, schema, sample values, table rows, and raster/vector tile data · Advisory · geolens-io/geolens · GitHub
https://github.com/geolens-io/geolens/security/advisories/GHSA-p23g-mvhj-jh3jVendor Advisories for CVE-2026-55178(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 2 ecosystems)
PyPI(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| geolens | 0.0.0, 1.0.0, 1.2.0 | 1.2.3 | — |
| geolens-cli | 1.0.0, 1.2.0 | 1.2.3 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @geolens/sdk | — | 1.2.3 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 22:43 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 19:58 UTCEG score recompute
- 2026-09-19 06:53 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 04:35 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 15:30 UTCEG score recompute
- 2026-09-17 14:49 UTCEG score recompute
- 2026-09-16 21:56 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 15:34 UTCEG score recompute
- 2026-08-18 18:09 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55178?
When was CVE-2026-55178 disclosed?
Is CVE-2026-55178 actively exploited?
What is the CVSS score of CVE-2026-55178?
How do I remediate CVE-2026-55178?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55178
Is Your Infrastructure Affected by CVE-2026-55178?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.