Process crash via oversized TTF pattern
Published Jan 29, 2026 · Updated Jan 29, 2026
Heap corruption in GNOME Fonts Viewer 3.34.0 allows context-dependent attackers to crash the process via a crafted TTF font file. The parsing path processes an approximately 84,500-byte pattern appended to a TTF header, repeatedly calling malloc() until memory is exhausted. A user must open the malicious file in the viewer; the demonstrated outcome is a process crash, while repeated runs can freeze the host.
Summary
What happened
Heap corruption in GNOME Fonts Viewer 3.34.0 allows context-dependent attackers to crash the process via a crafted TTF font file. The parsing path processes an approximately 84,500-byte pattern appended to a TTF header, repeatedly calling malloc() until memory is exhausted. A user must open the malicious file in the viewer; the demonstrated outcome is a process crash, while repeated runs can freeze the host.
The record
- CVE
- CVE-2020-37011
- Published
- Jan 29, 2026
- Updated
- Jan 29, 2026
- Vendor
- XMLSoft
- Product
- Fonts
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2026CVE publishedPublication date reported by the CVE source.
- Jan 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.34.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Gnome Fonts Viewer 3.34.0 Heap Corruption exploitfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo