# CVE-2025-15270: FontForge SFD File Parsing Improper Validation of Array Index Remote Code Execution Vulnerability > Remote attackers can execute arbitrary code by tricking users into opening malicious SFD files due to improper array index validation. - **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 31 Dec 2025 - **Updated:** 31 Dec 2025 - **Also known as:** ALSA-2026:6628, ALSA-2026:6631, DEBIAN-CVE-2025-15270, GHSA-hp8x-4h95-9799, RHSA-2026:6628, RHSA-2026:6631, RHSA-2026:6635, RHSA-2026:7001, RHSA-2026:8875, RLSA-2026:6628, RLSA-2026:6631, SUSE-SU-2026:1636-1, SUSE-SU-2026:21375-1, UBUNTU-CVE-2025-15270, openSUSE-SU-2026:10513-1, openSUSE-SU-2026:20608-1 ## What is CVE-2025-15270? CVE-2025-15270 is a high-severity memory corruption vulnerability in FontForge, published on 31 Dec 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 SFD File Parsing Improper Validation of Array Index Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of FontForge. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of SFD files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated array. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-28563. Weakness: CWE-129 (Improper Validation of Array Index) ## Which versions are affected by CVE-2025-15270? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `fontforge` | AlmaLinux:10 | All versions | 20230101-15.el10_1 | | `fontforge` | AlmaLinux:9 | All versions | 20201107-8.el9_7 | | `fontforge` | Red Hat:enterprise_linux:10.1 | All versions | 0:20230101-15.el10_1 | | `fontforge-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:20230101-15.el10_1 | | `fontforge-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:20230101-15.el10_1 | | `fontforge` | Red Hat:enterprise_linux:9::crb | All versions | 0:20201107-8.el9_7 | | `fontforge-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:20201107-8.el9_7 | | `fontforge-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:20201107-8.el9_7 | | `fontforge` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:20230101-15.el10_0 | | `fontforge-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:20230101-15.el10_0 | | `fontforge-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:20230101-15.el10_0 | | `fontforge` | Red Hat:rhel_eus:9.4::crb | All versions | 0:20201107-7.el9_4 | | `fontforge-debuginfo` | Red Hat:rhel_eus:9.4::crb | All versions | 0:20201107-7.el9_4 | | `fontforge-debugsource` | Red Hat:rhel_eus:9.4::crb | All versions | 0:20201107-7.el9_4 | | `fontforge` | Red Hat:rhel_eus:9.6::crb | All versions | 0:20201107-8.el9_6 | | `fontforge-debuginfo` | Red Hat:rhel_eus:9.6::crb | All versions | 0:20201107-8.el9_6 | | `fontforge-debugsource` | Red Hat:rhel_eus:9.6::crb | All versions | 0:20201107-8.el9_6 | | `fontforge` | Rocky Linux:10 | All versions | 0:20230101-15.el10_1 | | `fontforge` | Rocky Linux:9 | All versions | 0:20201107-8.el9_7 | | `fontforge` | openSUSE:Leap 16.0 | All versions | 20251009-160000.2.1 | | `fontforge` | openSUSE:Tumbleweed | All versions | 20251009-6.1 | Products: Fontforge Fontforge. ## How do I fix CVE-2025-15270? Apply the vendor's patch. ## Is CVE-2025-15270 being exploited? There is no known exploitation of CVE-2025-15270 in the wild and no public exploit code. ## Other vulnerabilities in FontForge - [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-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) - [CVE-2025-15273](https://insights.sbomify.com/CVE-2025-15273/): FontForge PFB File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-15270 and fix it if it is affected. What it is: CVE-2025-15270 is a high-severity memory corruption vulnerability in FontForge, published on 31 Dec 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: There is no known exploitation of CVE-2025-15270 in the wild and no public exploit code. Affected product: FontForge. 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-15270/ (Markdown: https://insights.sbomify.com/CVE-2025-15270/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15270 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15270 - OSV: https://osv.dev/vulnerability/CVE-2025-15270 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-15270/ Summaries are generated and may contain mistakes; the official description above is the record.