# CVE-2026-112052: libspatialite through 5.1.0 Integer Overflow in WKB Geometry Parsing

> Attackers can cause crashes or heap corruption in libspatialite by supplying crafted geometry data with large point counts, primarily affecting 32-bit builds.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112052, ECHO-2bfc-22c6-43e5, GHSA-8jmj-j7pf-v8j3, UBUNTU-CVE-2026-112052

## What is CVE-2026-112052?

CVE-2026-112052 is a medium-severity vulnerability in libspatialite, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

libspatialite through 5.1.0 contains an integer overflow vulnerability in the WKB point and vertex count size guard of ParseWkbLine and related parsers in gg_wkb.c, allowing out-of-bounds reads. Attackers can supply a crafted geometry BLOB with a large point count, for example in a SpatiaLite database file, to crash the process or corrupt heap memory on 32-bit builds.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-112052?


## How do I fix CVE-2026-112052?

No fix has been published for CVE-2026-112052 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112052 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112052 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112052 and fix it if it is affected.

What it is: CVE-2026-112052 is a medium-severity vulnerability in libspatialite, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112052 exists.

Affected product: libspatialite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112052/ (Markdown: https://insights.sbomify.com/CVE-2026-112052/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112052
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112052
- OSV: https://osv.dev/vulnerability/CVE-2026-112052

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112052/
Summaries are generated and may contain mistakes; the official description above is the record.