CVE-2025-50951: fontforge · Memory Leak
Affects fontforgeSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfontforge/fontforgepkg:github/fontforge/fontforgeOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Monitor official FontForge repositories and security advisories closely for patches addressing CVE-2025-50951 and apply updates promptly once available.
- Restrict access to FontForge applications and font processing services to trusted users only, minimizing exposure to untrusted font files.
- Implement strict validation and sandboxing of font files before processing to detect and isolate potentially malicious inputs.
- Educate users about the risks of opening font files from untrusted sources to reduce the likelihood of user interaction-based exploitation.
- Employ memory usage monitoring and alerting on systems running FontForge to detect abnormal memory consumption indicative of exploitation attempts.
- Consider using alternative font editing tools temporarily if feasible, especially in critical production environments.
- For automated pipelines, introduce additional scanning or filtering steps to identify malformed or suspicious font files prior to processing.
- Maintain robust backup and recovery procedures to minimize operational impact in case of denial of service incidents.
Description
FontForge v20230101 was discovered to contain a memory leak via the utf7toutf8_copy function at /fontforge/sfd.c.