Bug 2426434 (CVE-2025-15270) - CVE-2025-15270 fontforge: FontForge: Remote Code Execution via malicious SFD file parsing
Summary: CVE-2025-15270 fontforge: FontForge: Remote Code Execution via malicious SFD ...
Keywords:
Status: NEW
Alias: CVE-2025-15270
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2426579 2426580
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-31 08:02 UTC by OSIDB Bzimport
Modified: 2026-04-30 10:35 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:6628 0 None None None 2026-04-06 05:19:23 UTC
Red Hat Product Errata RHSA-2026:6631 0 None None None 2026-04-06 06:32:57 UTC
Red Hat Product Errata RHSA-2026:6635 0 None None None 2026-04-06 07:47:49 UTC
Red Hat Product Errata RHSA-2026:7001 0 None None None 2026-04-08 07:17:40 UTC
Red Hat Product Errata RHSA-2026:7677 0 None None None 2026-04-13 02:23:44 UTC
Red Hat Product Errata RHSA-2026:8875 0 None None None 2026-04-20 02:09:59 UTC

Description OSIDB Bzimport 2025-12-31 08:02:09 UTC
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.

Comment 2 errata-xmlrpc 2026-04-06 05:19:23 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:6628 https://access.redhat.com/errata/RHSA-2026:6628

Comment 3 errata-xmlrpc 2026-04-06 06:32:56 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:6631 https://access.redhat.com/errata/RHSA-2026:6631

Comment 4 errata-xmlrpc 2026-04-06 07:47:48 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:6635 https://access.redhat.com/errata/RHSA-2026:6635

Comment 5 errata-xmlrpc 2026-04-08 07:17:39 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

Via RHSA-2026:7001 https://access.redhat.com/errata/RHSA-2026:7001

Comment 6 errata-xmlrpc 2026-04-13 02:23:43 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:7677 https://access.redhat.com/errata/RHSA-2026:7677

Comment 7 errata-xmlrpc 2026-04-20 02:09:58 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:8875 https://access.redhat.com/errata/RHSA-2026:8875


Note You need to log in before you can comment on or make changes to this bug.