CVE-2026-9501: GNU LibreDWG Dwgread Utility decode.c decompress_R2004_section assertion
A vulnerability was determined in GNU LibreDWG up to 0.14. The impacted element is the function decompress_R2004_section of the file src/decode.c of the component Dwgread Utility. Executing a manipulation can lead to reachable assertion. The attack is restricted to local execution. The exploit has been publicly disclosed and may be utilized. This patch is called e501cb9926c1e9a07a0d1cc997f3e69e9be801c9. A patch should be applied to remediate this issue.
CVE-2026-9501 is a crash-type flaw in GNU LibreDWG's dwgread utility. A crafted or malformed DWG file can trigger an assertion in LibreDWG 0.14 and earlier when processed locally. The documented impact is availability loss for the utility, not data theft or remote compromise.
Executive priority
Prioritize remediation for engineering, CAD, conversion, or file-ingestion systems that handle outside DWG files. This is a moderate availability issue, not a confirmed remote compromise path, but public disclosure increases operational urgency.
Technical view
The issue is CWE-617 reachable assertion in src/decode.c, function decompress_R2004_section, affecting GNU LibreDWG versions 0.1 through 0.14. The CVSS v4.0 vector is local, low complexity, low privileges, no user interaction, with low availability impact. A patch is identified as commit e501cb9926c1e9a07a0d1cc997f3e69e9be801c9.
Likely exposure
Exposure is most likely where LibreDWG dwgread or dependent local workflows process DWG files, especially files received from outside trusted channels. The source bundle does not identify network services, cloud defaults, or downstream packaged products as affected.
Exploitation context
The bundle states public exploit material has been disclosed and may be used, but KEV is false and no cited source confirms active exploitation. Attack requirements are local execution with low privileges. Treat untrusted DWG processing as the main risk scenario.
Researcher notes
Key evidence points to a reachable assertion in decompress_R2004_section and a patch commit. The provided materials do not establish active exploitation, broader product inheritance, or confidentiality and integrity impact. Further analysis should stay focused on local DWG parsing exposure and fixed-code verification.
Mitigation direction
Apply the LibreDWG patch identified as commit e501cb9926c1e9a07a0d1cc997f3e69e9be801c9.
Upgrade affected LibreDWG versions 0.14 and earlier when vendor packages include the fix.
Avoid processing untrusted DWG files with vulnerable dwgread builds.
Run DWG conversion or inspection workflows in isolated, least-privilege environments.
Check GNU LibreDWG and distribution vendor guidance for packaged remediation details.
Validation and detection
Inventory systems and pipelines using GNU LibreDWG or dwgread.
Confirm installed versions are newer than 0.14 or include the patch commit.
Review local workflows that accept externally supplied DWG files.
Check logs for dwgread crashes or assertion failures during DWG parsing.
Verify regression tests pass after applying the vendor fix.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-617: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.