# CVE-2025-50949: Denial of service in n/a

> A memory leak in FontForge's DlgCreate8 component allows attackers to cause a denial of service by exhausting system memory.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-50949, GHSA-hw5f-q2pp-q95m, OESA-2025-2601, OESA-2025-2602, OESA-2025-2603, OESA-2025-2604, OESA-2025-2605, OESA-2025-2643, SUSE-SU-2025:4353-1, SUSE-SU-2026:20016-1, UBUNTU-CVE-2025-50949, openSUSE-SU-2025:15758-1, openSUSE-SU-2025:20174-1

## What is CVE-2025-50949?

CVE-2025-50949 is a medium-severity denial of service vulnerability in n/a, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2025-50949?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fontforge` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 20200314-150200.3.12.1 |
| `fontforge` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP7 | All versions | 20200314-150200.3.12.1 |
| `fontforge` | SUSE:Linux Enterprise Server 16.0 | All versions | 20230101-160000.3.1 |
| `fontforge` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 20230101-160000.3.1 |
| `fontforge` | openSUSE:Leap 15.6 | All versions | 20200314-150200.3.12.1 |
| `fontforge` | openSUSE:Leap 16.0 | All versions | 20230101-160000.3.1 |
| `fontforge` | openSUSE:Tumbleweed | All versions | 20251009-2.1 |

Products: Fontforge Fontforge.

## How do I fix CVE-2025-50949?

Upgrade to a fixed version.

## Is CVE-2025-50949 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50949 exists.

## Other vulnerabilities in n/a

- [CVE-2019-15785](https://insights.sbomify.com/CVE-2019-15785/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-15269](https://insights.sbomify.com/CVE-2025-15269/): FontForge SFD File Parsing Use-After-Free Remote Code Execution Vulnerability (high 8.8)
- [CVE-2025-15270](https://insights.sbomify.com/CVE-2025-15270/): FontForge SFD File Parsing Improper Validation of Array Index Remote Code Execution Vulnerability (high 8.8)
- [CVE-2025-15271](https://insights.sbomify.com/CVE-2025-15271/): FontForge SFD File Parsing Improper Validation of Array Index Remote Code Execution Vulnerability (high 8.8)
- [CVE-2025-15272](https://insights.sbomify.com/CVE-2025-15272/): FontForge SFD File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50949 and fix it if it is affected.

What it is: CVE-2025-50949 is a medium-severity denial of service vulnerability in n/a, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50949 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-50949/ (Markdown: https://insights.sbomify.com/CVE-2025-50949/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-50949
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-50949
- OSV: https://osv.dev/vulnerability/CVE-2025-50949

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-50949/
Summaries are generated and may contain mistakes; the official description above is the record.