CVE-2025-50949VulnerabilityPublished 23 Oct 2025Updated 24 Oct 2025

CVE-2025-50949: fontforge · n/a

Affects fontforgeSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubfontforge/fontforge`pkg:github/fontforge/fontforge`Other threats	Affected =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

Until an official patch is released, European organizations should implement several specific mitigations: 1) Restrict the use of FontForge to trusted users and environments, limiting exposure to untrusted or external font files. 2) Implement strict file validation and scanning for font files before opening them in FontForge, using antivirus and sandboxing techniques. 3) Monitor system memory usage closely on machines running FontForge to detect abnormal increases that may indicate exploitation attempts. 4) Educate users about the risks of opening font files from unknown or untrusted sources to reduce the likelihood of triggering the vulnerability. 5) Where possible, isolate FontForge usage in virtual machines or containers to limit the impact of potential crashes. 6) Maintain up-to-date backups of work to mitigate disruption from application failures. 7) Engage with FontForge developers or community to track patch releases and apply updates promptly once available. 8) Consider alternative font editing tools if immediate risk reduction is necessary and FontForge cannot be secured.

Description

FontForge v20230101 was discovered to contain a memory leak via the component DlgCreate8.

Impact

For European organizations, the primary impact of CVE-2025-50949 is on availability. Organizations relying on FontForge for font design, publishing, or software development may experience application crashes or degraded performance due to memory exhaustion. This could disrupt creative workflows, delay project timelines, and increase operational costs. While the vulnerability does not compromise data confidentiality or integrity, denial-of-service conditions can affect productivity and service reliability. In sectors such as digital media, publishing houses, graphic design firms, and software companies, this could have a tangible operational impact. Additionally, if FontForge is integrated into automated pipelines or CI/CD systems for font processing, the vulnerability could cause broader service interruptions. The lack of known exploits reduces immediate risk, but the requirement for user interaction means phishing or social engineering could be used to trigger the vulnerability. Organizations should consider the risk in the context of their use of FontForge and exposure to untrusted font files.

CWE-401Missing Release of Memory after Effective Lifetime (opens in a new tab)
Variant weaknessLikelihood of exploit: Medium
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Implementation · Libraries or Frameworks
Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Architecture and Design · Build and Compilation
Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/fontforge/fontforge/pull/5491 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2025, 07:36 UTC

WeaknessesCWE-401

Technical details

References

Community reviews

Related threats