Quick answers
- Is CVE-2026-63272 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63272 being exploited in the wild.
- How severe is CVE-2026-63272?
- Informational severity, published 22 September 2026.
- Which products and versions are affected?
- LibreOffice before 26.2.5.
- Is there a fix for CVE-2026-63272?
- A patch was published on 2026-09-21: Fixed in LibreOffice 26.2.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63272 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63272?
- Check whether you run LibreOffice at an affected version. 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
The vulnerability is a classic bounds check failure in WMF text record parsing: the count of advance width values and text length are read independently from the file without validation that they match. During rendering, the code iterates through characters and indexes the advance array by position, causing an out-of-bounds read/write when the array is exhausted before the text ends. The fix validates that advance arrays match text length and ignores shorter arrays.
Affected products
- LibreOffice LibreOffice before 26.2.5
Timeline
- 2026-09-21: disclosed
- 2026-09-21: patched: Fixed in LibreOffice 26.2.5