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.
CVE-2025-27363
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-05-06), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.1 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 9.0(high)
- EPSS
- 97.8%
- KEV
- ⚠ Exploited
Published
March 11, 2025
Last Modified
April 20, 2026
Advisory Details (10)
Auto-updated May 19, 2026oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/14/3oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/14/2oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/14/1oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/13/8oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/13/3oss-security - CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/13/2oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/13/12oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/13/11oss-security - CVE-2025-27363: out of bounds write in FreeType <= 2.13.0
http://www.openwall.com/lists/oss-security/2025/03/13/1CVE-2025-27363
https://www.facebook.com/security/advisories/cve-2025-27363Vendor Advisories for CVE-2025-27363(17)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2025-27363Microsoft Security Response Center (MSRC)High
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.
- RHSA-2025:9380Red Hat Product SecurityHigh
Red Hat Security Advisory: spice-client-win security update
- RHSA-2025:8292Red Hat Product SecurityHigh
Red Hat Security Advisory: mingw-freetype and spice-client-win security update
- RHSA-2025:8253Red Hat Product SecurityHigh
Red Hat Security Advisory: spice-client-win security update
- RHSA-2025:8219Red Hat Product SecurityHigh
Red Hat Security Advisory: spice-client-win security update
- RHSA-2025:8195Red Hat Product SecurityHigh
Red Hat Security Advisory: mingw-freetype and spice-client-win security update
- RHSA-2025:3573Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.12.75 packages and security update
- RHSA-2025:3421Red Hat Product SecurityHigh
Red Hat Security Advisory: freetype security update
- +9 more
Patch Availability(18)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libfreetype6-dev (2.6.1-0.1ubuntu2.5+esm2) @ xenial | 2026-07-16 | ubuntu |
| ubuntu | libfreetype6-dev (2.11.1+dfsg-1ubuntu0.3) @ jammy | 2026-07-16 | ubuntu |
| redhat | spice-client-win-0:8.2-1 | 2025-06-23 | redhat |
| redhat | spice-client-win-0:8.10-1 | 2025-05-29 | redhat |
| redhat | spice-client-win-0:8.4-2 | 2025-05-28 | redhat |
| redhat | spice-client-win-0:8.6-1 | 2025-05-27 | redhat |
| redhat | spice-client-win-0:8.8-5 | 2025-05-27 | redhat |
| redhat | rhcos-412.86.202503310142-0 | 2025-04-10 | redhat |
| redhat | freetype-0:2.9.1-7.el8_4 | 2025-03-31 | redhat |
| redhat | freetype-0:2.9.1-5.el8_2.1 | 2025-03-31 | redhat |
| redhat | freetype-0:2.10.4-10.el9_2 | 2025-03-31 | redhat |
| redhat | freetype-0:2.8-15.el7_9.1 | 2025-03-31 | redhat |
| redhat | freetype-0:2.9.1-6.el8_6.3 | 2025-03-31 | redhat |
| redhat | freetype-0:2.9.1-10.el8_8 | 2025-03-31 | redhat |
| redhat | freetype-0:2.10.4-10.el9_5 | 2025-03-31 | redhat |
| redhat | freetype-0:2.10.4-10.el9_4 | 2025-03-31 | redhat |
| redhat | freetype-0:2.9.1-10.el8_10 | 2025-03-31 | redhat |
| redhat | freetype-0:2.10.4-7.el9_0 | 2025-03-31 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 133× in last 7d / 558× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 923 total refreshes for this CVE.
- 2026-07-16 18:28 UTCEG score recompute
- 2026-07-16 18:28 UTCVendor advisory
- 2026-07-16 18:28 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 14:13 UTCEG score recompute
- 2026-07-16 14:13 UTCVendor advisory
- 2026-07-16 14:12 UTCGHSA enrichment
- 2026-07-16 09:58 UTCEG score recompute
- 2026-07-16 09:58 UTCVendor advisory
- 2026-07-16 09:58 UTCGHSA enrichment
- 2026-07-16 05:44 UTCEG score recompute
- 2026-07-16 05:44 UTCVendor advisory
- 2026-07-16 05:44 UTCGHSA enrichment
- 2026-07-16 01:29 UTCEG score recompute
- 2026-07-16 01:29 UTCVendor advisory
- 2026-07-16 01:29 UTCGHSA enrichment
- 2026-07-15 21:14 UTCEG score recompute
- 2026-07-15 21:14 UTCVendor advisory
- 2026-07-15 21:14 UTCGHSA enrichment
- 2026-07-15 16:59 UTCEG score recompute
- 2026-07-15 16:59 UTCVendor advisory
- 2026-07-15 16:58 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 12:44 UTCEG score recompute
- 2026-07-15 12:44 UTCVendor advisory
- 2026-07-15 12:43 UTCGHSA enrichment
- 2026-07-15 08:29 UTCEG score recompute
- 2026-07-15 08:29 UTCVendor advisory
- 2026-07-15 08:28 UTCGHSA enrichment
- 2026-07-15 04:14 UTCEG score recompute
- 2026-07-15 04:14 UTCVendor advisory
- 2026-07-15 04:13 UTCGHSA enrichment
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-14 23:59 UTCEG score recompute
- 2026-07-14 23:59 UTCVendor advisory
- 2026-07-14 23:59 UTCGHSA enrichment
- 2026-07-14 19:45 UTCEG score recompute
- 2026-07-14 19:45 UTCVendor advisory
- 2026-07-14 19:45 UTCGHSA enrichment
- 2026-07-14 18:05 UTCCISA KEV update
- 2026-07-14 15:30 UTCEG score recompute
- 2026-07-14 15:30 UTCVendor advisory
- 2026-07-14 15:30 UTCGHSA enrichment
- 2026-07-14 11:16 UTCEG score recompute
- 2026-07-14 11:16 UTCVendor advisory
- 2026-07-14 11:16 UTCGHSA enrichment
- 2026-07-14 07:01 UTCEG score recompute
- 2026-07-14 07:01 UTCVendor advisory
- 2026-07-14 07:01 UTCGHSA enrichment
- 2026-07-14 02:46 UTCEG score recompute
- 2026-07-14 02:46 UTCVendor advisory
- 2026-07-14 02:46 UTCGHSA enrichment
- 2026-07-13 22:32 UTCEG score recompute
- 2026-07-13 22:32 UTCVendor advisory
- 2026-07-13 22:32 UTCGHSA enrichment
- 2026-07-13 22:29 UTCEPSS rescore
- 2026-07-13 18:18 UTCEG score recompute
- 2026-07-13 18:18 UTCVendor advisory
- 2026-07-13 18:17 UTCGHSA enrichment
- 2026-07-13 17:07 UTCCISA KEV update
- 2026-07-13 14:03 UTCEG score recompute
- 2026-07-13 14:03 UTCVendor advisory
- 2026-07-13 14:03 UTCGHSA enrichment
- 2026-07-13 09:48 UTCEG score recompute
- 2026-07-13 09:48 UTCVendor advisory
- 2026-07-13 09:48 UTCGHSA enrichment
- 2026-07-13 05:33 UTCEG score recompute
- 2026-07-13 05:33 UTCVendor advisory
- 2026-07-13 05:33 UTCGHSA enrichment
- 2026-07-13 01:18 UTCEG score recompute
- 2026-07-13 01:18 UTCVendor advisory
- 2026-07-13 01:18 UTCGHSA enrichment
- 2026-07-12 21:03 UTCEG score recompute
- 2026-07-12 21:03 UTCVendor advisory
- 2026-07-12 21:02 UTCGHSA enrichment
- 2026-07-12 16:47 UTCEG score recompute
- 2026-07-12 16:47 UTCVendor advisory
- 2026-07-12 16:46 UTCGHSA enrichment
- 2026-07-12 12:32 UTCEG score recompute
- 2026-07-12 12:32 UTCVendor advisory
- 2026-07-12 12:32 UTCGHSA enrichment
- 2026-07-12 08:17 UTCEG score recompute
- 2026-07-12 08:17 UTCVendor advisory
- 2026-07-12 08:17 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 04:02 UTCEG score recompute
- 2026-07-12 04:02 UTCVendor advisory
- 2026-07-12 04:02 UTCGHSA enrichment
- 2026-07-11 23:46 UTCEG score recompute
- 2026-07-11 23:46 UTCVendor advisory
- 2026-07-11 23:46 UTCGHSA enrichment
- 2026-07-11 19:31 UTCEG score recompute
- 2026-07-11 19:31 UTCVendor advisory
- 2026-07-11 19:31 UTCGHSA enrichment
Publicly available exploits
(3 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCtin-z/CVE-2025-27363First seen Jul 23, 2025
Integer overflow in FreeType software, which also affects Chrome
Open source ↗ - Open source ↗GitHub PoCov3rf1ow/CVE-2025-27363First seen May 26, 2025
- Open source ↗GitHub PoCzhuowei/CVE-2025-27363-proof-of-conceptFirst seen Mar 23, 2025
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc · redhat
Same CWE
10 shownCWE-787
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2011-2462EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
- CVE-2010-4398NVD 7.8EG 9.0 KEVEPSS 95%HIGH
- CVE-2010-3333NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-2883NVD 7.3EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-1297NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3953NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3129NVD 7.8EG 9.0 KEVEPSS 100%HIGH
Frequently asked(6)
What is CVE-2025-27363?
When was CVE-2025-27363 disclosed?
Is CVE-2025-27363 actively exploited?
What is the CVSS score of CVE-2025-27363?
Which products are affected by CVE-2025-27363?
How do I remediate CVE-2025-27363?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-27363
Is Your Infrastructure Affected by CVE-2025-27363?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.