FreeType Out-of-Bounds Write Vulnerability
FreeType — FreeType
An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.
8.1
27.8%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- Mar 11, 2025
- Modified
- Jun 17, 2026
- Added to KEV
- May 6, 2025
- Federal patch due
- May 27, 2025
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
3 foundWeaponization
Public repositories whose name or description references CVE-2025-27363, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
References
Frequently asked questions
What is CVE-2025-27363?
An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.
How severe is CVE-2025-27363?
CVE-2025-27363 has a CVSS base score of 8.1 out of 10 (CVSS 3.1).
Is CVE-2025-27363 actively exploited in the wild?
Yes. CVE-2025-27363 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added May 6, 2025, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-27363?
27.8% - meaning FIRST.org's EPSS model estimates a 27.8% probability this vulnerability will be exploited in the wild within 30 days (98% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2025-27363?
We found 3 public GitHub repositories referencing CVE-2025-27363, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2025-27363?
CVE-2025-27363 is classified under CWE-787 (CWE-787 Out-of-bounds Write).
Cross-checked against
Impactr finds and proves whether CVE-2025-27363 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist