---
id: "CVE-2026-112059"
kind: "vulnerability"
aliases: ["CVE-2026-112059"]
title: "libLAS: heap overflow in point reader lets crafted LAS files corrupt memory"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["geospatial", "libas", "lidar", "package", "point-cloud", "self-hosted"]
not_affected_if: ["liblas-not-installed", "no-untrusted-las-files"]
published_at: "2026-10-18T13:16:38+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T03:40:57+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112059", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# libLAS: heap overflow in point reader lets crafted LAS files corrupt memory

libLAS through 1.8.1 truncates the schema size to 16 bits when sizing the point buffer, so a crafted .las file with an oversized LASSchema record causes a heap out-of-bounds write. An attacker who supplies such a file can corrupt memory and crash tools like lasinfo, las2las or las2txt, and may be able to run code.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `lasinfo --version` or check the installed libLAS package version and compare it with `1.8.1`
- Check whether the `lasinfo`, `las2las` or `las2txt` binaries are installed on hosts that process untrusted LAS files
- unknown whether the sources list a patched version

## Fix

- Move libLAS past `1.8.1` once a patched release is available; unknown whether one exists yet
- Until then, do not process LAS files from untrusted sources with lasinfo, las2las or las2txt
- unknown whether the sources give a workaround beyond that

## Timeline

- 2026-10-23T21:57:15+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112059

## From the sources

libLAS through 1.8.1 contains a heap out-of-bounds write vulnerability in the point record reader caused by truncating the schema byte size to 16 bits when sizing the point buffer. Attackers can craft a .las file with a LASSchema variable length record whose schema exceeds 65535 bytes, so tools like lasinfo, las2las, or las2txt write attacker-controlled bytes past the heap buffer, causing memory corruption and crashes.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_