CVE-2025-27363
Published: May 6, 2025
Official Description
FreeType contains an out-of-bounds write vulnerability when attempting to parse font subglyph structures related to TrueType GX and variable font files that may allow for arbitrary code execution.
CISA KEV Advisory
FreeType Out-of-Bounds Write Vulnerability
FreeType contains an out-of-bounds write vulnerability when attempting to parse font subglyph structures related to TrueType GX and variable font files that may allow for arbitrary code execution.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Risk Analysis
FreeType contains an out-of-bounds write vulnerability when parsing font subglyph structures, which could lead to arbitrary code execution. The high EPSS score of 0.76154 suggests a strong likelihood of exploitation, and its presence in CISA's KEV confirms that this flaw is actively being exploited.
This vulnerability is actively being exploited in the wild, as confirmed by its inclusion in CISA's KEV.
Update FreeType to a patched version to mitigate the risk of arbitrary code execution. Ensure all systems using FreeType are kept current with security updates.
Technical Analysis
CVE-2025-27363 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2025-27363 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2025-27363 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1