Vulnerability in Spatialite Libspatialite
CVE-2026-112048
libspatialite through 5.1.0 fails to validate the polygon ring count in ParseWkbPolygon, allowing attackers to trigger uncontrolled interior-ring allocation via crafted geometry BLOBs. Attackers can supply a crafted polygon in a SpatiaLite database or ST_GeomFromWKB input to crash the process or corrupt heap memory on 32-bit builds.
Published .
CVSS v3 metric
CVSS v3 base score 6.1 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- hackmd.io/@haindpwn/libspatialite-wkb-geometry-count-overflow (third-party-advisory)
- www.gaia-gis.it/fossil/libspatialite/file (technical-description)
- www.vulncheck.com/advisories/libspatialite-through-5.1.0-uncontrolled-memory-al… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-112048?
- CVE-2026-112048 is a medium-severity vulnerability in Spatialite Libspatialite, classified under CWE-789. CVSS score: 6.1/10. Published 2026-10-18.
- How severe is CVE-2026-112048?
- Medium severity. CVSS v3 base score is 6.1 out of 10.