# CVE-2026-110606: LibreCAD libdxfrw through LC2.2.0 Stack Out-of-Bounds Read via dwgReader18::readFileHeader

> Attackers can cause a crash or read stack memory by providing a crafted DWG file to LibreCAD due to an out-of-bounds read in the libdxfrw library.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/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:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110606, GHSA-v4r9-37cv-99h9, UBUNTU-CVE-2026-110606, openSUSE-SU-2026:12156-1

## What is CVE-2026-110606?

CVE-2026-110606 is a medium-severity memory corruption vulnerability in LibreCAD, 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

LibreCAD libdxfrw through LC2.2.0 (LibreCAD through 2.2.1.5) contains a stack-based out-of-bounds read vulnerability in dwgReader18::readFileHeader() caused by calling strlen on non-NUL-terminated buffers. Attackers can supply a crafted AC1018, AC1024 or AC1027 DWG file without NUL bytes in the decrypted header to read adjacent stack memory and crash the process.

Weakness: CWE-125 (Out-of-bounds Read)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `librecad` | openSUSE:Tumbleweed | All versions | 2.2.1.5-2.1 |

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

Apply the vendor's patch.

## Is CVE-2026-110606 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110606 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110606 is a medium-severity memory corruption vulnerability in LibreCAD, 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110606 exists.

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

## Sources

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

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