GeoLens is a self-hosted geospatial data catalog with semantic search, OGC and STAC APIs, and a map builder. Prior to v1.2.3, the catalog’s 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. As a result, a cross‑dataset authorization bypass allows an attacker to traverse these paths. When a public map references a private dataset, anonymous callers can use GET /maps/{id} and GET /maps/{id}/style.json to obtain private layer 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. If a public source dataset has a relationship to a private target dataset, anonymous callers can enumerate that relationship via the dataset relationship APIs 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.

Any GeoLens deployment built from the open‑source project prior to the release of v1.2.3 is affected. This includes all versions that still use the legacy authorization logic, regardless of operating system or configuration. The vendor’s fix is delivered in release v1.2.3, so systems on older versions or that have not applied the patch remain vulnerable.

The CVSS score of 7.5 indicates a moderate‑high severity vulnerability that primarily jeopardizes data confidentiality. The EPSS score is very low (< 1%) and the vulnerability is not listed in CISA’s KEV catalog. Attackers can exploit the flaw by issuing standard HTTP requests to public endpoints without authentication; the absence of visibility checks allows anonymous users or users with the default editor role to read private layer data, sample values, vector tiles, raster pixels, table rows, schemas, or enumeration of relationships. The attack vector is straightforward, the barrier to entry is low, and the potential impact is significant in environments where anonymous access or public maps are enabled.