LibreDWG
GNU
- Product type
- Other
- Catalog vulnerabilities
- 99
Severity across 11 analyzed records
- Products & ServicesProducts & Services
- SolutionsSolutions
- PricingPricing
- CompanyCompany
- ResourcesResources
en
en
Verify to analyze this security profile
As of 09/14/2026, within CyStack's analyzed data, LibreDWG has 3 security vulnerabilities published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of LibreDWG and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-15520GNU LibreDWG R2004 Section Decompression decode.c decompress_R2004_section heap-based overflow | Exploitation statusPublic exploit | FixYes | Published07/13/2026 | SeverityMedium |
CVE-2026-15184GNU LibreDWG DWG File dwg.c dwg_next_entity null pointer dereference | Exploitation statusPublic exploit | FixYes | Published07/09/2026 | SeverityMedium |
CVE-2026-15182GNU LibreDWG BMP Image dwg.c dwg_bmp heap-based overflow | Exploitation statusPublic exploit | FixYes | Published07/09/2026 | SeverityMedium |
CVE-2026-9605GNU libredwg Dwgbmp Utility bits.c bit_read_RC heap-based overflow | Exploitation statusPublic exploit | FixYes | Published05/26/2026 | SeverityMedium |
CVE-2026-9530GNU LibreDWG Dwgbmp Utility decode.c read_2004_compressed_section out-of-bounds | Exploitation statusPublic exploit | FixYes | Published05/26/2026 | SeverityMedium |
CVE-2026-9529GNU LibreDWG Dwggrep Utility dwggrep.c match_BLOCK_HEADER null pointer dereference | Exploitation statusPublic exploit | FixNot confirmed | Published05/26/2026 | SeverityMedium |
CVE-2026-9504GNU LibreDWG Dwggrep Utility dwggrep.c bit_convert_TU out-of-bounds | Exploitation statusPublic exploit | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-9503GNU LibreDWG DWG File decode.c dwg_next_entity null pointer dereference | Exploitation statusPublic exploit | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-9502GNU LibreDWG Dwgread Utility decode.c decompress_R2004_section heap-based overflow | Exploitation statusPublic exploit | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-9501GNU LibreDWG Dwgread Utility decode.c decompress_R2004_section assertion | Exploitation statusPublic exploit | FixYes | Published05/25/2026 | SeverityMedium |
CVE-2026-9500GNU LibreDWG Dwgread Utility decode.c read_2004_compressed_section heap-based overflow | Exploitation statusPublic exploit | FixNot confirmed | Published05/25/2026 | SeverityMedium |
CVE-2025-61154 | Exploitation statusNot known exploited | FixNot confirmed | Published03/12/2026 | SeverityMedium |
CVE-2023-26157 | Exploitation statusNot known exploited | FixYes | Published01/02/2024 | SeverityMedium |
CVE-2023-36272 | Exploitation statusPublic exploit | FixNot confirmed | Published06/23/2023 | SeverityHigh |
CVE-2023-36273 | Exploitation statusPublic exploit | FixNot confirmed | Published06/23/2023 | SeverityUnknown |
CVE-2023-36271 | Exploitation statusPublic exploit | FixNot confirmed | Published06/23/2023 | SeverityUnknown |
CVE-2023-36274 | Exploitation statusNot known exploited | FixNot confirmed | Published06/23/2023 | SeverityUnknown |
CVE-2023-25222 | Exploitation statusPublic exploit | FixNot confirmed | Published03/01/2023 | SeverityUnknown |
CVE-2022-45332 | Exploitation statusPublic exploit | FixNot confirmed | Published11/30/2022 | SeverityHigh |
CVE-2022-35164 | Exploitation statusNot confirmed | FixNot confirmed | Published08/18/2022 | SeverityUnknown |
CVE-2022-33034 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33033 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33032 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33025 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33028 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33027 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33026 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2022-33024 | Exploitation statusNot confirmed | FixNot confirmed | Published06/22/2022 | SeverityUnknown |
CVE-2021-42586 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2022 | SeverityUnknown |
CVE-2021-42585 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2022 | SeverityUnknown |
CVE-2021-45950 | Exploitation statusNot confirmed | FixNot confirmed | Published12/31/2021 | SeverityUnknown |
CVE-2021-28237 | Exploitation statusNot confirmed | FixNot confirmed | Published12/02/2021 | SeverityUnknown |
CVE-2021-28236 | Exploitation statusNot confirmed | FixNot confirmed | Published12/02/2021 | SeverityUnknown |
CVE-2021-39525 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-39523 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-39527 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-39528 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-39530 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-39521 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-39522 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2021 | SeverityUnknown |
CVE-2021-36080 | Exploitation statusNot confirmed | FixNot confirmed | Published07/01/2021 | SeverityUnknown |
CVE-2020-23861 | Exploitation statusNot confirmed | FixNot confirmed | Published05/18/2021 | SeverityUnknown |
CVE-2020-21831 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21844 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21843 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21842 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21841 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21840 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21839 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21838 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21836 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21835 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21834 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21833 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21832 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21830 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21827 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21819 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21818 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21817 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21815 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21816 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21814 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-21813 | Exploitation statusNot confirmed | FixNot confirmed | Published05/17/2021 | SeverityUnknown |
CVE-2020-15807 | Exploitation statusNot confirmed | FixNot confirmed | Published07/17/2020 | SeverityUnknown |
CVE-2019-20909 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2019-20910 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2019-20911 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2019-20912 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2019-20913 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2019-20914 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2019-20915 | Exploitation statusNot confirmed | FixNot confirmed | Published07/16/2020 | SeverityUnknown |
CVE-2020-6609 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2020-6610 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2020-6611 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2020-6612 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2020-6613 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2020-6614 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2020-6615 | Exploitation statusNot confirmed | FixNot confirmed | Published01/08/2020 | SeverityUnknown |
CVE-2019-20009 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-20011 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-20012 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-20013 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-20014 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-20015 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-20010 | Exploitation statusNot confirmed | FixNot confirmed | Published12/27/2019 | SeverityUnknown |
CVE-2019-9776 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9775 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9772 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9770 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9778 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9774 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9773 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9771 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9779 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2019-9777 | Exploitation statusNot confirmed | FixNot confirmed | Published03/14/2019 | SeverityUnknown |
CVE-2018-14524 | Exploitation statusNot confirmed | FixNot confirmed | Published07/23/2018 | SeverityUnknown |
CVE-2018-14471 | Exploitation statusNot confirmed | FixNot confirmed | Published07/20/2018 | SeverityUnknown |
CVE-2018-14443 | Exploitation statusNot confirmed | FixNot confirmed | Published07/20/2018 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
