# CVE-2026-110603: LASzip through 3.5.0 Invalid Free via Truncated VLR Header in laszip_read_header

> Attackers can cause heap corruption and crashes by providing crafted LAS/LAZ files with truncated VLR headers to applications using LASzip.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/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:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110603, GHSA-m6xh-mjq9-hv5w, UBUNTU-CVE-2026-110603

## What is CVE-2026-110603?

CVE-2026-110603 is a medium-severity memory corruption vulnerability in rapidlasso LASzip, published on 14 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

LASzip through 3.5.0 contains an invalid free vulnerability in laszip_read_header() that allows attackers to free uninitialized heap pointers via truncated variable length record data. Attackers can supply a crafted LAS/LAZ file with an inflated VLR count that, when opened and destroyed through the C API, crashes the process and corrupts the heap.

Weakness: CWE-824 (Access of Uninitialized Pointer)

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


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

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

## Is CVE-2026-110603 being exploited?

There is no known exploitation of CVE-2026-110603 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110603 is a medium-severity memory corruption vulnerability in rapidlasso LASzip, published on 14 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: There is no known exploitation of CVE-2026-110603 in the wild and no public exploit code.

Affected product: rapidlasso LASzip. 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-110603/ (Markdown: https://insights.sbomify.com/CVE-2026-110603/index.md)
```

## Sources

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

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