LOW 3.3

CVE-2026-15184: GNU LibreDWG Null Pointer Dereference Denial of Service

GNU LibreDWG versions up to 0.13.4 contain a flaw in how the DWG file handler processes certain file structures. When a specially crafted DWG file is opened, the software can crash due to a null pointer dereference. An attacker with local access to a system could exploit this to cause a denial of service. The issue requires user interaction—specifically opening a malicious file—and affects only the availability of the application, not data confidentiality or integrity. Version 0.14 and later resolve this issue.

Source data · NVD / CISA · public domain

CVSS
3.1 · 3.3 LOW · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Weaknesses (CWE)
CWE-404, CWE-476
Affected products
0 configuration(s)
Published / Modified
2026-07-09 / 2026-07-09

NVD description (verbatim)

A vulnerability was found in GNU LibreDWG up to 0.13.4. The impacted element is the function dwg_next_entity of the file src/dwg.c of the component DWG File Handler. Performing a manipulation of the argument next_obj results in null pointer dereference. The attack must be initiated from a local position. The exploit has been made public and could be used. Upgrading to version 0.14 is sufficient to resolve this issue. The patch is named dde45dac3c4d902e4d8fed150a8017b9732019c9. Upgrading the affected component is recommended. Different than CVE-2026-9503.

9 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

The vulnerability exists in the dwg_next_entity function located in src/dwg.c of the GNU LibreDWG DWG file handler component. The root cause is improper handling of the next_obj argument, which can be manipulated by a crafted DWG file to trigger a null pointer dereference condition. The flaw is classified under CWE-404 (Improper Resource Validation) and CWE-476 (Null Pointer Dereference), indicating insufficient validation of input parameters before dereferencing. Exploitation is limited to local attackers with the ability to load files, and requires no elevated privileges.

Business impact

Organizations using GNU LibreDWG for DWG file processing face application availability risk if users open untrusted or compromised DWG files. While data theft or system compromise is not possible through this vulnerability, repeated crashes could disrupt design workflows or document processing pipelines. The impact is primarily operational rather than security-critical, though organizations handling DWG files from external or untrusted sources should evaluate whether denial-of-service conditions pose business continuity concerns.

Affected systems

GNU LibreDWG library versions 0.13.4 and earlier are affected. Any application or service that embeds or uses LibreDWG for parsing DWG files is potentially at risk. This includes CAD software, file conversion utilities, and document processing systems that depend on this library. Version 0.14 and later are not affected.

Exploitability

The exploit proof-of-concept has been publicly disclosed, reducing the barrier to weaponization. However, exploitation requires local file system access and user action to open a malicious DWG file. The attack cannot be triggered remotely or without user interaction. The CVSS score of 3.3 (LOW) reflects these constraints: local attack vector, low privileges required, and no impact on confidentiality or integrity—only denial of service. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog, but public disclosure of the technique warrants prompt patching to prevent opportunistic exploitation.

Remediation

Upgrade GNU LibreDWG to version 0.14 or later. This version includes commit dde45dac3c4d902e4d8fed150a8017b9732019c9, which resolves the null pointer dereference. Organizations should verify the specific patch version against their vendor's advisory to ensure compatibility with dependent applications. If immediate upgrade is not possible, restrict access to untrusted DWG files and educate users not to open files from unverified sources.

Patch guidance

Apply GNU LibreDWG version 0.14 or later to all systems and applications using the library. Test the upgrade in a staging environment first to ensure compatibility with dependent CAD or document processing tools. Verify the installation includes commit dde45dac3c4d902e4d8fed150a8017b9732019c9. Check the vendor's release notes for any breaking changes or dependency updates. If your distribution or application vendor provides LibreDWG as a bundled dependency, coordinate with their release schedule; do not attempt manual patching unless explicitly supported.

Detection guidance

Monitor system logs for repeated application crashes or exceptions in processes that use LibreDWG, particularly when opening DWG files. Look for null pointer dereference errors in dwg_next_entity or related stack traces. File integrity monitoring can detect unauthorized DWG file modifications. Additionally, audit file access logs to identify attempts to open DWG files from suspicious sources. In a controlled environment, test parsing of known-malicious DWG samples (if available) against unpatched versions to confirm the crash behavior and validate that patched versions handle the input safely.

Why prioritize this

Although the CVSS score is LOW (3.3), this vulnerability merits timely attention because public exploit disclosure accelerates adoption by threat actors. Local attackers or malicious insiders could use a crafted DWG file to disrupt design workflows or trigger denial of service. Organizations with CAD environments, engineering teams, or document processing pipelines should prioritize patching to maintain operational continuity. The effort to upgrade is typically low, making it a high-return remediation action.

Risk score, explained

The CVSS 3.1 score of 3.3 reflects a local attack vector (AV:L), low attack complexity (AC:L), low privilege requirement (PR:L), no user interaction beyond opening a file (UI:N), unchanged scope (S:U), and availability impact only (A:L). This translates to a LOW severity rating because the vulnerability cannot be exploited remotely, requires local access and a user to open a malicious file, and causes only a denial of service. However, the public disclosure of an exploit technique means real-world risk may exceed the base score in environments where insider threats or local file-sharing is common.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. The attack vector is local only—an attacker must have access to the file system or convince a user to open a crafted DWG file. Remote exploitation is not possible.

What happens if a user opens a malicious DWG file?

The application using LibreDWG will likely crash with a null pointer dereference error. This causes a denial of service to that application but does not result in data theft, system compromise, or privilege escalation.

Is this the same as CVE-2026-9503?

No. According to the vulnerability record, this is explicitly different from CVE-2026-9503. Both are LibreDWG issues but involve different code paths or mechanisms.

What should organizations do if they cannot upgrade immediately?

Restrict user access to DWG files from untrusted sources, implement file integrity monitoring, and educate staff not to open unsolicited or suspicious DWG files. Monitor for application crashes and plan an upgrade timeline as soon as possible.

This analysis is provided for informational purposes and reflects publicly available information as of the publication date. Organizations should verify all patch versions, affected product lists, and remediation steps against official vendor advisories before taking action. SEC.co does not provide warranties regarding the completeness or accuracy of third-party vulnerability data. Testing should be conducted in a non-production environment before deploying patches. For the most current information, consult the GNU LibreDWG project repository and official security notices. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).