Quick answers
- Is CVE-2026-6039 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6039 being exploited in the wild.
- How severe is CVE-2026-6039?
- Informational severity, with a CVSS score of 5.4, published 15 June 2026.
- Which products and versions are affected?
- The Document Foundation LibreOffice.
- Is there a fix for CVE-2026-6039?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-6039 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-6039?
- Check whether you run The Document Foundation LibreOffice. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap buffer overflow exists in LibreOffice's DXF (Drawing Exchange Format) import component. The vulnerability is caused by a numeric truncation error (CWE-197) where the point count for a polyline is truncated to a 16-bit value when allocating the point buffer, but the original, larger count is used when filling the buffer. This results in an out-of-bounds write (CWE-787) past the end of the heap-allocated memory. An attacker can exploit this by inducing a user to open a maliciously crafted DXF file. Successful exploitation can lead to a denial of service (application crash) or potentially arbitrary code execution in the context of the user. The issue is addressed in fixed versions by rejecting polylines with oversized point counts.
Affected products
- The Document Foundation LibreOffice
Timeline
- 2026-06-15: disclosed
- 2026-06-15: advisory