CVE-2025-27363
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.
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H- facebook.com/security/advisories/cve-2025-27363Third Party Advisory
- openwall.com/lists/oss-security/2025/03/13/1Mailing List
- openwall.com/lists/oss-security/2025/03/13/11Mailing List
- openwall.com/lists/oss-security/2025/03/13/12Mailing List
- openwall.com/lists/oss-security/2025/03/13/2Mailing List
- openwall.com/lists/oss-security/2025/03/13/3Mailing List
- openwall.com/lists/oss-security/2025/03/13/8Mailing List
- openwall.com/lists/oss-security/2025/03/14/1Mailing List
- openwall.com/lists/oss-security/2025/03/14/2Mailing List
- openwall.com/lists/oss-security/2025/03/14/3Mailing List
- openwall.com/lists/oss-security/2025/03/14/4Mailing List
- openwall.com/lists/oss-security/2025/05/06/3Mailing List
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 519 days
- CVSS
- 8.1 HIGH
- EPSS (30-day exploit probability)
- 27.8% · top 2% of all CVEs
- Weakness
- CWE-787
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.