# CVE-2025-27363: FreeType Out-of-Bounds Write

> Out-of-bounds write in FreeType allows arbitrary code execution via malicious TrueType GX or variable font files.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C/CR:H/IR:H/AR:H/MAV:N/MAC:L/MPR:N/MUI:N/MS:U/MC:H/MI:H/MA:H`)
- **Exploited in the wild:** Yes, since 6 May 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2025
- **Updated:** 19 Apr 2026
- **Also known as:** A-399065987, ALPINE-CVE-2025-27363, ALSA-2025:3421, ASB-A-399065987, AZL-58354, BELL-CVE-2025-27363, CLSA-2025-1742926404, CLSA-2025-1745956171, CLSA-2025-1750780979, CLSA-2025-1755681299, CLSA-2026-1787310855, DEBIAN-CVE-2025-27363, DLA-4104-1, DSA-5880-1, GHSA-g8qj-jv5h-78cp, JLSEC-2026-460, MGASA-2025-0099, OESA-2025-1300, RHSA-2025:3382, RHSA-2025:3383, RHSA-2025:3384, RHSA-2025:3385, RHSA-2025:3386, RHSA-2025:3387, RHSA-2025:3393, RHSA-2025:3395, RHSA-2025:3407, RHSA-2025:3421, RHSA-2025:8195, RHSA-2025:8219, RHSA-2025:8253, RHSA-2025:9380, RLSA-2025:3407, RLSA-2025:3421, ROOT-OS-ALPINE-315-CVE-2025-27363, SUSE-SU-2025:0960-1, SUSE-SU-2025:0998-1, UBUNTU-CVE-2025-27363, USN-7352-1

## What is CVE-2025-27363?

CVE-2025-27363 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-27363?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `freetype` | AlmaLinux:8 | All versions | 2.9.1-10.el8_10 |
| `freetype-devel` | AlmaLinux:8 | All versions | 2.9.1-10.el8_10 |
| `freetype` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.1-10.el8_10 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.1-10.el8_10 |
| `freetype-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.1-10.el8_10 |
| `freetype-demos-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.1-10.el8_10 |
| `freetype-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.1-10.el8_10 |
| `freetype` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.10.4-10.el9_5 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.10.4-10.el9_5 |
| `freetype-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.10.4-10.el9_5 |
| `freetype-demos-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.10.4-10.el9_5 |
| `freetype-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.10.4-10.el9_5 |
| `freetype` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.10.4-10.el9_5 |
| `freetype-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.10.4-10.el9_5 |
| `freetype-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.10.4-10.el9_5 |
| `freetype-demos-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.10.4-10.el9_5 |
| `spice-client-win` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:8.2-1.el8_2 |
| `spice-client-win-x64` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:8.2-1.el8_2 |
| `spice-client-win-x86` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:8.2-1.el8_2 |
| `freetype` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.1-5.el8_2.1 |
| `freetype-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.1-5.el8_2.1 |
| `freetype-debugsource` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.1-5.el8_2.1 |
| `freetype-demos-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.1-5.el8_2.1 |
| `freetype-devel` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:2.9.1-5.el8_2.1 |
| `spice-client-win` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:8.4-2.el8_4 |
| `spice-client-win-x64` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:8.4-2.el8_4 |
| `spice-client-win-x86` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:8.4-2.el8_4 |
| `freetype` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.9.1-7.el8_4 |
| `freetype-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.9.1-7.el8_4 |
| `freetype-debugsource` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.9.1-7.el8_4 |
| `freetype-demos-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.9.1-7.el8_4 |
| `freetype-devel` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:2.9.1-7.el8_4 |
| `spice-client-win` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:8.6-1.el8_6 |
| `spice-client-win-x64` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:8.6-1.el8_6 |
| `spice-client-win-x86` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:8.6-1.el8_6 |
| `freetype` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.9.1-6.el8_6.3 |
| `freetype-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.9.1-6.el8_6.3 |
| `freetype-debugsource` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.9.1-6.el8_6.3 |
| `freetype-demos-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.9.1-6.el8_6.3 |
| `freetype-devel` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:2.9.1-6.el8_6.3 |

Products: Debian Debian Linux, Freetype Freetype.

## How do I fix CVE-2025-27363?

Upgrade to a fixed version. US federal agencies must fix it by 27 May 2025.

## Is CVE-2025-27363 being exploited?

Yes. Attackers have exploited CVE-2025-27363 in the wild since at least 6 May 2025.

Public exploit code:

- https://github.com/zhuowei/CVE-2025-27363-proof-of-concept (github_poc): https://github.com/zhuowei/CVE-2025-27363-proof-of-concept
- Integer overflow in FreeType software, which also affects Chrome (github_poc): https://github.com/tin-z/CVE-2025-27363
- https://github.com/ov3rf1ow/CVE-2025-27363 (github_poc): https://github.com/ov3rf1ow/CVE-2025-27363

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27363 and fix it if it is affected.

What it is: CVE-2025-27363 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-27363 in the wild since at least 6 May 2025.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27363/ (Markdown: https://insights.sbomify.com/CVE-2025-27363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27363
- OSV: https://osv.dev/vulnerability/CVE-2025-27363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27363/
Summaries are generated and may contain mistakes; the official description above is the record.