# CVE-2026-9605: GNU libredwg Dwgbmp Utility bits.c bit_read_RC heap-based overflow

> A heap-based buffer overflow in GNU libredwg's Dwgbmp utility allows remote attackers to execute arbitrary code or cause denial of service via crafted files.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-9fj3-rp2j-9wq6

## What is CVE-2026-9605?

CVE-2026-9605 is a medium-severity memory corruption vulnerability in GNU libredwg, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in GNU libredwg up to 0.13.4.8160. This issue affects the function bit_read_RC of the file bits.c of the component Dwgbmp Utility. This manipulation causes heap-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been published and may be used. Patch name: 8f03865f37f5d4ffd616fef802acc980be54d300. Applying a patch is the recommended action to fix this issue.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Apply the vendor's patch.

## Is CVE-2026-9605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9605 is a medium-severity memory corruption vulnerability in GNU libredwg, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9605 exists.

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

## Sources

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

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