CVE-2026-63276: Stack buffer overflow in CFF to Type 1 font conversion

Published Sep 22, 2026
·
Updated

LibreOffice converts CFF fonts to Type 1 when it subsets a font, which happens when a document is exported to PDF, and CFF fonts may be embedded in documents. A stack buffer overflow existed in that conversion. The converted operators were written into a fixed size buffer with no check that they still fit, so a glyph emitting many operators wrote past the end of the buffer. In fixed versions the remaining capacity is tracked and the conversion stops when it is used up.

Affected Software

1 affected component
The Document Foundation LibreOffice

Event History

Sep 22, 2026
CVE Published
via MITRE·11:10 AM
Data Sourced
via MITRE·11:10 AM
DescriptionWeakness
Data Sourced
via NVD·12:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

When can the vulnerable conversion path be reached?

It is reached when LibreOffice subsets a CFF font, which occurs when exporting a document to PDF. CFF fonts can be embedded in documents, so a document containing such a font can trigger the conversion during export.

2

What is required to trigger the overflow?

A CFF glyph must emit enough converted operators to exceed the fixed-size stack buffer used by the CFF-to-Type-1 conversion. The overflow occurs because the vulnerable conversion did not check whether additional operators still fit in that buffer.

3

How do fixed versions prevent this issue?

Fixed versions track the remaining buffer capacity during conversion and stop the conversion when that capacity is exhausted.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203