Bug 2426421 (CVE-2025-15279)

Summary:	CVE-2025-15279 fontforge: FontForge: Remote Code Execution via heap-based buffer overflow in BMP file parsing
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	rhel-process-autobot, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in FontForge. This heap-based buffer overflow vulnerability occurs during the parsing of pixels within BMP (Bitmap) files, due to insufficient validation of user-supplied data length. A remote attacker could exploit this by tricking a user into opening a malicious BMP file or visiting a malicious page. Successful exploitation could lead to arbitrary code execution in the context of the current user.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2426593, 2426597
Bug Blocks:

Description OSIDB Bzimport 2025-12-31 08:01:09 UTC

FontForge GUtils BMP File Parsing Heap-based Buffer Overflow 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 pixels within BMP files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-27517.

Comment 2 errata-xmlrpc 2026-02-05 07:39:59 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

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

Comment 3 errata-xmlrpc 2026-02-09 01:32:51 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

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

Comment 4 errata-xmlrpc 2026-02-09 01:33:04 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

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

Comment 5 errata-xmlrpc 2026-02-09 01:39:15 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

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

Comment 6 errata-xmlrpc 2026-02-11 14:55:28 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.4 Extended Update Support

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

Comment 7 errata-xmlrpc 2026-04-13 02:23:39 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 8 errata-xmlrpc 2026-04-20 10:01:08 UTC

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7 Extended Lifecycle Support

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