libspatialite through 5.1.0 allows an attacker to supply a polygon geometry with an unvalidated ring count, causing the ParseWkbPolygon routine to allocate an uncontrolled number of interior‑ring structures. This flaw leads to a crash or heap corruption on 32‑bit builds. The weakness is a classic uncontrolled memory allocation vulnerability (CWE-770). The resulting heap corruption could potentially enable arbitrary code execution, but such an outcome is inferred rather than explicitly documented in the CVE description.

The vulnerability impacts the libspatialite component of SpatiaLite up to and including version 5.1.0. Systems that use any 32‑bit build of this library and process user‑provided geometry—such as database records stored in SpatiaLite or direct calls to ST_GeomFromWKB—are at risk. Applications that embed libspatialite as a dependency, regardless of language, are also affected when the vulnerable versions are present.

A CVSS score of 6.9 indicates moderate severity, and the absence of EPSS data and a KEV listing suggests that exploitation likelihood is currently low to moderate. The vulnerability can be exploited by injecting a crafted WKB polygon that contains an oversized ring count; the attack vector therefore requires the ability to influence input processed by libspatialite. It is inferred that, on 32‑bit builds, a successful exploit that corrupts heap memory could be escalated to arbitrary code execution, but no confirmed exploitation evidence is provided.