# CVE-2026-9530: GNU LibreDWG Dwgbmp Utility decode.c read_2004_compressed_section out-of-bounds

> A local attacker can trigger an out-of-bounds read in the Dwgbmp utility, potentially causing information disclosure or application crashes.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-x5hm-p5rv-v4c7

## What is CVE-2026-9530?

CVE-2026-9530 is a medium-severity memory corruption vulnerability in GNU LibreDWG, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in GNU LibreDWG up to 0.14. The impacted element is the function read_2004_compressed_section of the file src/decode.c of the component Dwgbmp Utility. Executing a manipulation can lead to out-of-bounds read. The attack requires local access. The exploit has been made available to the public and could be used for attacks. This patch is called 8f03865f37f5d4ffd616fef802acc980be54d300. It is advisable to implement a patch to correct this issue.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Apply the vendor's patch.

## Is CVE-2026-9530 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9530 is a medium-severity memory corruption vulnerability in GNU LibreDWG, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9530 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-9530/ (Markdown: https://insights.sbomify.com/CVE-2026-9530/index.md)
```

## Sources

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

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