How severe is CVE-2026-6039?

CVE-2026-6039 has a CVSS 4.0 base score of 5.4, rated medium severity.

Is CVE-2026-6039 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-6039?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-6039 have an EU (EUVD) identifier?

Yes. CVE-2026-6039 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36734.

When was CVE-2026-6039 published?

CVE-2026-6039 was published on 2026-06-15 and last updated on 2026-06-17.

CVE-2026-6039

CVE-2026-6039 is a medium-severity vulnerability with a CVSS 4.0 base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-197.

Key facts

Severity: Medium (CVSS 4.0 base score 5.4)
EPSS exploit prediction: 0% (5th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-36734
Weakness: CWE-197
Published: 2026-06-15
Last modified: 2026-06-17

Description

LibreOffice can import drawings in the DXF format used by CAD software. A heap buffer overflow existed when importing a DXF polyline. The point count taken from the file was truncated to a 16-bit value when the point buffer was sized, while the full count was used to fill it, so a polyline whose point count exceeded the 16-bit range was written past the end of the buffer. In fixed versions such oversized polylines are rejected.

Frequently asked questions

What is CVE-2026-6039?: LibreOffice can import drawings in the DXF format used by CAD software. A heap buffer overflow existed when importing a DXF polyline. The point count taken from the file was truncated to a 16-bit value when the point buffer was sized, while the full count was used to fill it, so a polyline whose point count exceeded the 16-bit range was written past the end of the buffer. In fixed versions such oversized polylines are rejected.
How severe is CVE-2026-6039?: CVE-2026-6039 has a CVSS 4.0 base score of 5.4, rated medium severity.
Is CVE-2026-6039 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (5th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-6039?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-6039 have an EU (EUVD) identifier?: Yes. CVE-2026-6039 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36734.
When was CVE-2026-6039 published?: CVE-2026-6039 was published on 2026-06-15 and last updated on 2026-06-17.

References

https://www.libreoffice.org/about-us/security/advisories/cve-2026-6039

Other CWE-197 vulnerabilities

CVE-2024-43639 — Critical (CVSS 9.8): Windows KDC Proxy Remote Code Execution Vulnerability
CVE-2020-15202 — Critical (CVSS 9.0): In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last…
CVE-2024-49018 — High (CVSS 8.8): SQL Server Native Client Remote Code Execution Vulnerability
CVE-2024-43519 — High (CVSS 8.8): Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability
CVE-2024-30009 — High (CVSS 8.8): Windows Routing and Remote Access Service (RRAS) Remote Code Execution Vulnerability
CVE-2023-32143 — High (CVSS 8.8): D-Link DAP-1360 webupg UPGCGI_CheckAuth Numeric Truncation Remote Code Execution Vulnerability. This vulnerability…

Browse all CWE-197 vulnerabilities →