A vulnerability was determined in GNU LibreDWG 0.13.4-154-g0b573035. This impacts the function decompress_R2004_section of the file src/decode.c of the component R2004 Section Decompression. Executing a manipulation can lead to heap-based buffer overflow. The attack requires local access. The exploit has been publicly disclosed and may be utilized. Upgrading to version 0.14.8396 will fix this issue. This patch is called 3d0f9fc2eddbd6579c99af3111c37c98f03475d0. You should upgrade the affected component.
CVE-2026-15520
This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 13, 2026
Advisory Details (5)
Auto-updated Jul 13, 20260.14.8396
Patch available: LibreDWG/libredwg 0.14.8396 (pre-release)
https://github.com/LibreDWG/libredwg/releases/tag/0.14.8396commit 3d0f9fc2eddb (LibreDWG/libredwg)
Fix landed in LibreDWG/libredwg commit 3d0f9fc2eddb — awaiting tagged release
https://github.com/LibreDWG/libredwg/commit/3d0f9fc2eddbd6579c99af3111c37c98f03475d0CVE-Repos/libredwg/libredwg_0b57303_heap_overflow_decompress_R2004_section.dwg at main · HackC0der/CVE-Repos · GitHub
https://github.com/HackC0der/CVE-Repos/blob/main/libredwg/libredwg_0b57303_heap_overflow_decompress_R2004_section.dwgHeap-buffer-overflow WRITE in decompress_R2004_section at decode.c:1295 (libredwg main branch @0b57303) · Issue #1251 · LibreDWG/libredwg · GitHub
https://github.com/LibreDWG/libredwg/issues/1251Vendor Advisories for CVE-2026-15520(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 02:18 UTCNVD updateCVSS v4 → 1.9
- 2026-07-13 01:48 UTCEG score recompute
- 2026-07-13 01:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-119
Frequently asked(4)
What is CVE-2026-15520?
When was CVE-2026-15520 disclosed?
What is the CVSS score of CVE-2026-15520?
How do I remediate CVE-2026-15520?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15520
Is Your Infrastructure Affected by CVE-2026-15520?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.