{"id":"CVE-2026-112048","kind":"vulnerability","aliases":["CVE-2026-112048"],"related":[],"title":"libspatialite: unchecked polygon ring count lets crafted geometry crash or corrupt memory","description":"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.","summary":"libspatialite through 5.1.0 does not validate the ring count when parsing WKB polygons, so a crafted geometry BLOB triggers uncontrolled interior-ring allocation. An attacker who supplies such a polygon to a SpatiaLite database or ST_GeomFromWKB can crash the process or corrupt heap memory on 32-bit builds.","severity":"medium","cvss":6.9,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["32-bit","gis","libspatialite","package","spatialite"],"not_affected_if":["trusted-input-only"],"how_to_check":"- Run `spatialite --version` or check the installed libspatialite version in your package manager, and compare it to `5.1.0`.\n- Check whether the application passes untrusted geometry (WKB BLOBs or ST_GeomFromWKB input) into SpatiaLite.\n- Check whether the build is 32-bit.","fix":"- Upgrade libspatialite past `5.1.0` to a release that contains the fix (unknown exact version in sources).\n- Until patched, reject or validate untrusted WKB input before it reaches SpatiaLite.","status":"open","published_at":"2026-10-18T13:16:36+00:00","first_seen_at":"2026-10-23T21:57:15+00:00","triaged_at":"2026-10-25T03:40:59+00:00","updated_at":"2026-10-25T03:40:59+00:00","category":"package","confidence":0.6,"triage":{"at":"2026-10-25T03:40:59Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade libspatialite past `5.1.0` to a release that contains the fix (unknown exact version in sources).\n- Until patched, reject or validate untrusted WKB input before it reaches SpatiaLite.","reach":"unknown","title":"libspatialite: unchecked polygon ring count lets crafted geometry crash or corrupt memory","impact":"medium","summary":"libspatialite through 5.1.0 does not validate the ring count when parsing WKB polygons, so a crafted geometry BLOB triggers uncontrolled interior-ring allocation. An attacker who supplies such a polygon to a SpatiaLite database or ST_GeomFromWKB can crash the process or corrupt heap memory on 32-bit builds.","category":"package","nicknames":[],"who_cares":["libspatialite","spatialite","gis","32-bit"],"confidence":0.6,"needs_auth":"unknown","worst_case":"Process crashes or heap memory is corrupted, possibly leading to code execution","analyst_note":"Confirm the fixed libspatialite version and whether 64-bit builds are affected, using the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-112048 and upstream release notes.","how_to_check":"- Run `spatialite --version` or check the installed libspatialite version in your package manager, and compare it to `5.1.0`.\n- Check whether the application passes untrusted geometry (WKB BLOBs or ST_GeomFromWKB input) into SpatiaLite.\n- Check whether the build is 32-bit.","needs_analyst":true,"not_affected_if":["trusted-input-only"],"who_is_affected":"Applications that load SpatiaLite databases or parse WKB geometry from untrusted sources are exposed, and the memory corruption described is stated for 32-bit builds. Systems using libspatialite only on trusted local data, or without accepting external geometry, are less exposed. The sources do not state which 64-bit builds are affected.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000698,"input_tokens":3359,"output_tokens":725,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-112048':15A,18A '-2026':14A,17A '32':19B,72B,123C '5.1.0':27B,77C 'alloc':48B,95C 'allow':87C 'attack':50B,88C,100C 'bit':20B,73B,124C 'blob':42B,99C 'build':74B,125C 'corrupt':11A,68B,119C 'count':5A,33B,84C 'craft':7A,40B,97C,104C 'crash':9A,64B,115C 'cve':13A,16A 'databas':59B,109C 'fail':78C 'geometri':8A,41B,98C 'geomfromwkb':62B,112C 'gis':21B 'heap':69B,120C 'input':113C 'interior':46B,93C 'interior-r':45B,92C 'let':6A 'libspatialit':1A,22B,25B,75C 'memori':12A,70B,121C 'packag':23B 'pars':35B 'parsewkbpolygon':86C 'polygon':3A,37B,55B,82C,105C 'process':66B,117C 'ring':4A,32B,47B,83C,94C 'spatialit':24B,58B,108C 'st':61B,111C 'suppli':52B,102C 'trigger':43B,90C 'uncheck':2A 'uncontrol':44B,91C 'valid':30B,80C 'via':96C 'wkb':36B","nicknames":[],"mitigations":[],"who_affected":"Applications that load SpatiaLite databases or parse WKB geometry from untrusted sources are exposed, and the memory corruption described is stated for 32-bit builds. Systems using libspatialite only on trusted local data, or without accepting external geometry, are less exposed. The sources do not state which 64-bit builds are affected.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-18T13:16:36+00:00","kev":null,"cvss_vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-112048","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-112048","severity":null,"published_at":"2026-10-18T13:16:36+00:00","modified_at":"2026-10-20T16:17:01+00:00","first_seen_at":"2026-10-23T21:57:15+00:00","fetched_at":"2026-10-23T22:28:55+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}