Skip to main content
VulnerabilityPublished Updated

CVE-2025-50951: fontforge · Memory Leak

Affects fontforgeSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GitHubfontforge/fontforgepkg:github/fontforge/fontforgeOther threatsAffected
  • =20230101
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor official FontForge repositories and security advisories closely for patches addressing CVE-2025-50951 and apply updates promptly once available.
  2. Restrict access to FontForge applications and font processing services to trusted users only, minimizing exposure to untrusted font files.
  3. Implement strict validation and sandboxing of font files before processing to detect and isolate potentially malicious inputs.
  4. Educate users about the risks of opening font files from untrusted sources to reduce the likelihood of user interaction-based exploitation.
  5. Employ memory usage monitoring and alerting on systems running FontForge to detect abnormal memory consumption indicative of exploitation attempts.
  6. Consider using alternative font editing tools temporarily if feasible, especially in critical production environments.
  7. For automated pipelines, introduce additional scanning or filtering steps to identify malformed or suspicious font files prior to processing.
  8. 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.

References

Community reviews

Loading reviews…