Quick answers
- Is CVE-2026-9529 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-9529 being exploited in the wild.
- How severe is CVE-2026-9529?
- Low severity, with a CVSS score of 3.3, published 26 May 2026.
- Which products and versions are affected?
- Gnu LibreDWG up to 0.14.
- Is there a fix for CVE-2026-9529?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-9529 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-9529?
- Check whether you run Gnu LibreDWG at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A null pointer dereference exists in the match_BLOCK_HEADER function within dwggrep.c of the GNU LibreDWG Dwggrep Utility. The vulnerability is triggered when the utility processes a malformed DWG file, leading to a segmentation fault (NULL pointer read access at address 0x0). An attacker with local access can exploit this to cause the application to crash. The issue was identified in the main branch at commit 6d6a339 and affects versions up to 0.14. Public exploit code in the form of a proof-of-concept DWG file has been released.
Affected products
- GNU LibreDWG up to 0.14
Timeline
- 2026-04-10: other: Vulnerability identified in commit 6d6a339
- 2026-05-26: disclosed: Vulnerability published via VulDB and NVD