CVE-2025-27363

CRITICALNVD 8.19.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 28%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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 v3
8.1
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
28%
EPSS %ILE
98th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://source.android.com/docs/security/bulletin/2025-05-01 · https://nvd.nist.gov/vuln/detail/CVE-2025-27363

Published

March 11, 2025

Last Modified

April 20, 2026

Advisory Details (10)

Auto-updated Oct 12, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available.
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/14/3
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/14/2
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/14/1
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/13/8
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/13/3
Web page

oss-security - CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/13/2
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/13/12
Web page

oss-security - Re: CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/13/11
Web page

oss-security - CVE-2025-27363: out of bounds write in FreeType <= 2.13.0

http://www.openwall.com/lists/oss-security/2025/03/13/1
Web page

CVE-2025-27363

https://www.facebook.com/security/advisories/cve-2025-27363

Vendor Advisories for CVE-2025-27363(18)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibfreetype6-dev (2.5.2-1ubuntu2.8+esm3) @ trusty2026-10-12ubuntu
ubuntulibfreetype6-dev (2.11.1+dfsg-1ubuntu0.3) @ jammy2026-10-12ubuntu
redhatspice-client-win-0:8.2-12025-06-23redhat
redhatspice-client-win-0:8.10-12025-05-29redhat
redhatspice-client-win-0:8.4-22025-05-28redhat
redhatspice-client-win-0:8.8-52025-05-27redhat
redhatspice-client-win-0:8.6-12025-05-27redhat
redhatopenshift/ose-rhel-coreos-8:412.86.202504240545-02025-05-08redhat
redhatopenshift/ose-rhel-coreos-8:412.86.202503310142-02025-04-10redhat
redhatfreetype-0:2.9.1-10.el8_82025-03-31redhat
redhatfreetype-0:2.8-15.el7_9.12025-03-31redhat
redhatfreetype-0:2.9.1-6.el8_6.32025-03-31redhat
redhatfreetype-0:2.9.1-10.el8_102025-03-31redhat
redhatfreetype-0:2.10.4-10.el9_52025-03-31redhat
redhatfreetype-0:2.10.4-7.el9_02025-03-31redhat
redhatfreetype-0:2.10.4-10.el9_22025-03-31redhat
redhatfreetype-0:2.9.1-5.el8_2.12025-03-31redhat
redhatfreetype-0:2.10.4-10.el9_42025-03-31redhat
redhatfreetype-0:2.9.1-7.el8_42025-03-31redhat

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.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
freetype—
  • every version up to 2.13.1-r0: fixed in 2.13.1-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
freetype—
  • every version up to 2.13.1-r0: fixed in 2.13.1-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
freetype—
  • every version up to 2.13.1-r0: fixed in 2.13.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
freetype2.10.4+dfsg-1, 2.10.4+dfsg-1+deb11u1
  • every version up to 2.10.4+dfsg-1+deb11u2: fixed in 2.10.4+dfsg-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
freetype2.12.1+dfsg-5, 2.12.1+dfsg-5+deb12u1, 2.12.1+dfsg-5+deb12u2, 2.12.1+dfsg-5+deb12u3
  • every version up to 2.12.1+dfsg-5+deb12u4: fixed in 2.12.1+dfsg-5+deb12u4
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
freetype—
  • every version up to 2.13.1+dfsg-1: fixed in 2.13.1+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
freetype—
  • every version up to 2.13.1+dfsg-1: fixed in 2.13.1+dfsg-1
—

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 59× in last 7d / 370× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 1,810 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 1,711 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 28% · 98th percentile
  2. 2026-10-15 15:23 UTCEG score recompute
  3. 2026-10-15 15:23 UTCVendor advisory
  4. 2026-10-15 15:23 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-10-14 16:31 UTCEPSS rescoreEPSS 28% · 98th percentile
  6. 2026-10-14 12:57 UTCEG score recompute
  7. 2026-10-14 12:57 UTCVendor advisory
  8. 2026-10-14 12:57 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-10-13 16:32 UTCEPSS rescoreEPSS 28% · 98th percentile
  10. 2026-10-13 10:32 UTCVendor advisory
  11. 2026-10-13 10:31 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-12 17:14 UTCEG score recompute
  13. 2026-10-12 16:32 UTCEPSS rescoreEPSS 28% · 98th percentile
  14. 2026-10-12 08:05 UTCVendor advisory
  15. 2026-10-12 08:05 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-12 03:49 UTCVendor advisory
  17. 2026-10-12 03:49 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-10-11 23:35 UTCVendor advisory
  19. 2026-10-11 23:34 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-10-11 19:19 UTCEG score recompute
  21. 2026-10-11 19:19 UTCVendor advisory
  22. 2026-10-11 19:19 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-11 18:57 UTCEG score recompute
  24. 2026-10-11 15:04 UTCEG score recompute
  25. 2026-10-11 15:04 UTCVendor advisory
Show 74 more
  1. 2026-10-11 15:04 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-10-11 13:47 UTCEPSS rescoreEPSS 28% · 98th percentile
  3. 2026-10-11 10:50 UTCVendor advisory
  4. 2026-10-11 10:50 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-10-11 06:36 UTCVendor advisory
  6. 2026-10-11 06:36 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-10-11 02:21 UTCVendor advisory
  8. 2026-10-11 02:21 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-10-10 22:06 UTCEG score recompute
  10. 2026-10-10 22:06 UTCVendor advisory
  11. 2026-10-10 22:06 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 28% · 98th percentile
  13. 2026-10-10 17:50 UTCVendor advisory
  14. 2026-10-10 17:50 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-10-10 13:35 UTCVendor advisory
  16. 2026-10-10 13:35 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-10-10 09:21 UTCVendor advisory
  18. 2026-10-10 09:21 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-10 05:07 UTCVendor advisory
  20. 2026-10-10 05:07 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-10-10 00:52 UTCVendor advisory
  22. 2026-10-10 00:52 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-09 20:37 UTCEG score recompute
  24. 2026-10-09 20:37 UTCVendor advisory
  25. 2026-10-09 20:37 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  26. 2026-10-09 20:06 UTCEPSS rescoreEPSS 28% · 98th percentile
  27. 2026-10-09 16:22 UTCVendor advisory
  28. 2026-10-09 16:22 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-10-09 12:06 UTCVendor advisory
  30. 2026-10-09 12:05 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  31. 2026-10-09 07:49 UTCVendor advisory
  32. 2026-10-09 07:49 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-10-09 03:35 UTCVendor advisory
  34. 2026-10-09 03:34 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  35. 2026-10-08 23:19 UTCVendor advisory
  36. 2026-10-08 23:19 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  37. 2026-10-08 19:05 UTCEG score recompute
  38. 2026-10-08 19:05 UTCVendor advisory
  39. 2026-10-08 19:05 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  40. 2026-10-08 17:09 UTCEPSS rescoreEPSS 28% · 98th percentile
  41. 2026-10-08 14:50 UTCVendor advisory
  42. 2026-10-08 14:50 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  43. 2026-10-08 10:34 UTCVendor advisory
  44. 2026-10-08 10:34 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-10-08 06:19 UTCVendor advisory
  46. 2026-10-08 06:19 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  47. 2026-10-08 02:04 UTCEG score recompute
  48. 2026-10-08 02:04 UTCVendor advisory
  49. 2026-10-08 02:04 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-10-07 23:46 UTCEPSS rescoreEPSS 28% · 98th percentile
  51. 2026-10-07 21:50 UTCVendor advisory
  52. 2026-10-07 21:50 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-10-07 17:35 UTCVendor advisory
  54. 2026-10-07 17:34 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-10-07 13:19 UTCVendor advisory
  56. 2026-10-07 13:19 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-10-07 09:05 UTCVendor advisory
  58. 2026-10-07 09:04 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-10-07 04:50 UTCVendor advisory
  60. 2026-10-07 04:50 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-10-07 00:36 UTCVendor advisory
  62. 2026-10-07 00:35 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-10-06 20:18 UTCVendor advisory
  64. 2026-10-06 20:18 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-10-06 16:04 UTCEG score recompute
  66. 2026-10-06 16:04 UTCVendor advisory
  67. 2026-10-06 16:04 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  68. 2026-10-06 15:16 UTCEPSS rescoreEPSS 28% · 98th percentile
  69. 2026-10-06 11:49 UTCVendor advisory
  70. 2026-10-06 11:49 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-10-06 07:34 UTCVendor advisory
  72. 2026-10-06 07:34 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-g8qj-jv5h-78cp · GitHub severity HIGH · GitHub CVSS 8.1
  74. 2026-10-06 03:19 UTCVendor advisory

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (3 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCtin-z/CVE-2025-27363
    Published Jul 23, 2025

    Integer overflow in FreeType software, which also affects Chrome

    Open source ↗
  • GitHub PoCov3rf1ow/CVE-2025-27363
    Published May 26, 2025
    Open source ↗
  • GitHub PoCzhuowei/CVE-2025-27363-proof-of-concept
    Published Mar 23, 2025
    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2025-27363?
CVE-2025-27363 is a critical-severity vulnerability; its CVE record was published on March 11, 2025. 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…
When was the CVE record for CVE-2025-27363 published?
The CVE record for CVE-2025-27363 was published on March 11, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 20, 2026; the record at its source may have been updated since.
Is CVE-2025-27363 actively exploited?
Yes. CISA added CVE-2025-27363 to the Known Exploited Vulnerabilities catalog on May 6, 2025, affecting FreeType FreeType. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2025-27363?
CVE-2025-27363 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2025-27363?
CVE-2025-27363 affects FreeType FreeType. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2025-27363?
A fix for CVE-2025-27363 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-27363 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-27363

Explore →

Is Your Infrastructure Affected by CVE-2025-27363?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs