Intel

AIKIDO-2026-10537

xarray-spatial is vulnerable to Path Traversal

Path Traversal Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Apr 24, 2026

60

Medium Risk

This Affects:

PYTHONxarray-spatial
0.9.2 - 0.9.6
Fixed in 0.9.7
Are you affected? Scan for Free

TL;DR

The native GeoTIFF/COG reader in open_geotiff / read_to_array and the VRT parser can act on untrusted file content: large declared dimensions and strip/tile paths can drive multi-gigabyte numpy / cupy allocations, a VRT can reference SourceFilename with .. that leaves the VRT directory before source paths are canonicalized with os.path.realpath(), and tiled layouts that do not match TileOffsets can desynchronize decoders. The vector rasterize() path, reproject output grid construction, and other raster hot paths (including some GPU predictors) previously sized buffers or windows without the same hard pixel caps, tile checks, and stride alignment that the release adds, so a crafted or pathological input can cause denial of service, directory escape when reading VRT-sourced rasters, or out-of-bounds or inconsistent memory access. The patch enforces max_pixels-style limits, path canonicalization, header/tile validation, and related bounds before allocation and decode.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range.

Background info

xarray-spatial is vulnerable to Path Traversal in versions 0.9.2 - 0.9.6.

How to fix this

Upgrade the xarray-spatial library to the patch version.