Low severity · published May 25, 2026
CVE-2026-9503
GNU LibreDWG DWG File decode.c dwg_next_entity null pointer dereference
3.3
CVSS
0.1%
EPSS
No
On KEV
Description
A security flaw has been discovered in GNU LibreDWG up to 0.14. This impacts the function dwg_next_entity of the file src/decode.c of the component DWG File Handler. The manipulation results in null pointer dereference. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. The patch is identified as 8f03865f37f5d4ffd616fef802acc980be54d300. Upgrading the affected component is advised.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
None
Availability
Low
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 1% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
LI
LibreDWG · GNU
0.1; 0.2; 0.3; 0.4; 0.5; 0.6; +8 more · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-9503
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-9503
github.com
https://github.com/HackC0der/CVE-Repos/blob/main/libredwg/libredwg_6d6a339_heap_oob_write_read_2004_compressed_section.dwg
github.com
https://github.com/LibreDWG/libredwg/commit/8f03865f37f5d4ffd616fef802acc980be54d300
github.com
https://github.com/LibreDWG/libredwg/issues/1245
vuldb.com
https://vuldb.com/submit/814260
vuldb.com
https://vuldb.com/vuln/365485
vuldb.com
https://vuldb.com/vuln/365485/cti
More from LibreDWG
9.8
CVE-2022-35164
LibreDWG v0.12.4.4608 & commit f2dea29 was discovered to contain a heap use-after-free via bit_copy_chain
9.8
CVE-2021-28237
LibreDWG v0.12.3 was discovered to contain a heap-buffer overflow via decode_preR13
9.8
CVE-2019-20914
An issue was discovered in GNU LibreDWG through 0.9.3
9.1
CVE-2019-9774
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645
9.1
CVE-2019-9775
An issue was discovered in GNU LibreDWG 0.7 and 0.7.1645
