CVE-2026-112048 SpatiaLite CVE debrief

Who should care

Defenders and administrators responsible for systems or applications using libspatialite should assess exposure and prioritize verification and updates to mitigate potential risks.

Why it matters

Defenders should care about CVE-2026-112048 because it affects libspatialite, which is used in various systems and applications. The vulnerability can cause process crashes or heap memory corruption, especially on 32-bit builds, from crafted geometry inputs. Verification and updates to libspatialite are crucial to mitigate these risks. Roles responsible for maintaining or securing systems using libspatialite should assess exposure and take action.

• Potential process crashes from crafted geometry inputs
• Potential heap memory corruption on 32-bit builds
• Verification priority for libspatialite versions and updates
• Defensive priority for restricting and monitoring geometry inputs

Technical summary

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. This can cause process crashes or heap memory corruption on 32-bit builds. The vulnerability is triggered through crafted polygon inputs in SpatiaLite databases or ST_GeomFromWKB functions, highlighting the need for defenders to prioritize verifying and updating libspatialite to mitigate potential crashes or memory corruption. Affected systems or applications should review and restrict input to SpatiaLite databases and ST_GeomFromWKB functions.

Defensive priority

Defenders should prioritize verifying and updating libspatialite to mitigate potential crashes or memory corruption from crafted geometry inputs.

Recommended defensive actions

• Verify libspatialite version and update to a fixed version if available
• Review and restrict input to SpatiaLite databases and ST_GeomFromWKB functions
• Monitor for and respond to potential crashes or memory corruption
• Perform an inventory of systems and applications using libspatialite to assess exposure
• Implement compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions and retest remediated assets to ensure successful mitigation
• technicalSummary

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in libspatialite, including its impact on 32-bit builds and potential for process crashes or heap memory corruption. The vulnerability is triggered by crafted geometry BLOBs, which can cause uncontrolled interior-ring allocation. The source details indicate that libspatialite versions up to 5.1.0 are affected. Defenders should verify libspatialite versions and update to a fixed version if available. The CVE Program record and NVD detail page offer additional context on

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.