CVE-2025-27363

CRITICALNVD 8.19.0
EchelonGraph scoreHIGH confidence

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_kev, epss, ghsa, nvd
Trending — 5 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)
CISA-KEV: ExploitedEPSS PROB: 26%CVSS: 8.1Exploit: cisa kev · ssvc active · epss top5pct · public exploitExposed: 0

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.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
26%
EPSS %ILE
98%
KEV
⚠ Exploited

Published

March 11, 2025

Last Modified

April 20, 2026

Advisory Details (10)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

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
generic

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
generic

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
generic🔴 Active Exploitation

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
generic🔴 Active Exploitation

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
generic🔴 Active Exploitation

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
generic

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
generic🔴 Active Exploitation

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
generic🔴 Active Exploitation

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
generic🔴 Active Exploitation

CVE-2025-27363

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

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

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibfreetype6-dev (2.6.1-0.1ubuntu2.5+esm2) @ xenial2026-07-27ubuntu
ubuntulibfreetype6-dev (2.11.1+dfsg-1ubuntu0.3) @ jammy2026-07-27ubuntu
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.6-12025-05-27redhat
redhatspice-client-win-0:8.8-52025-05-27redhat
redhatrhcos-412.86.202503310142-02025-04-10redhat
redhatfreetype-0:2.9.1-7.el8_42025-03-31redhat
redhatfreetype-0:2.9.1-5.el8_2.12025-03-31redhat
redhatfreetype-0:2.10.4-10.el9_22025-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_82025-03-31redhat
redhatfreetype-0:2.10.4-10.el9_52025-03-31redhat
redhatfreetype-0:2.10.4-10.el9_42025-03-31redhat
redhatfreetype-0:2.9.1-10.el8_102025-03-31redhat
redhatfreetype-0:2.10.4-7.el9_02025-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.

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 64× in last 7d / 363× 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 767 total refreshes for this CVE.

  1. 2026-07-27 07:36 UTCVendor advisory
  2. 2026-07-27 07:36 UTCGHSA enrichment
  3. 2026-07-27 03:22 UTCVendor advisory
  4. 2026-07-27 03:22 UTCGHSA enrichment
  5. 2026-07-26 23:06 UTCVendor advisory
  6. 2026-07-26 23:06 UTCGHSA enrichment
  7. 2026-07-26 18:51 UTCEG score recompute
  8. 2026-07-26 18:51 UTCVendor advisory
  9. 2026-07-26 18:50 UTCGHSA enrichment
  10. 2026-07-26 14:53 UTCEPSS rescore
  11. 2026-07-26 14:34 UTCEG score recompute
  12. 2026-07-26 14:34 UTCVendor advisory
  13. 2026-07-26 14:34 UTCGHSA enrichment
  14. 2026-07-26 10:20 UTCVendor advisory
  15. 2026-07-26 10:20 UTCGHSA enrichment
  16. 2026-07-26 06:04 UTCVendor advisory
  17. 2026-07-26 06:03 UTCGHSA enrichment
  18. 2026-07-26 01:49 UTCEG score recompute
  19. 2026-07-26 01:49 UTCVendor advisory
  20. 2026-07-26 01:49 UTCGHSA enrichment
  21. 2026-07-25 14:17 UTCEPSS rescore
  22. 2026-07-24 14:17 UTCEPSS rescore
  23. 2026-07-23 02:52 UTCEG score recompute
  24. 2026-07-22 23:05 UTCEG score recompute
  25. 2026-07-22 23:05 UTCVendor advisory
Show 75 more
  1. 2026-07-22 23:05 UTCGHSA enrichment
  2. 2026-07-22 19:40 UTCCISA KEV update
  3. 2026-07-22 18:50 UTCVendor advisory
  4. 2026-07-22 18:50 UTCGHSA enrichment
  5. 2026-07-22 14:35 UTCEG score recompute
  6. 2026-07-22 14:35 UTCVendor advisory
  7. 2026-07-22 14:34 UTCGHSA enrichment
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-22 14:07 UTCEPSS rescore
  10. 2026-07-22 10:19 UTCVendor advisory
  11. 2026-07-22 10:19 UTCGHSA enrichment
  12. 2026-07-22 06:04 UTCVendor advisory
  13. 2026-07-22 06:04 UTCGHSA enrichment
  14. 2026-07-22 01:50 UTCVendor advisory
  15. 2026-07-22 01:50 UTCGHSA enrichment
  16. 2026-07-21 21:35 UTCVendor advisory
  17. 2026-07-21 21:35 UTCGHSA enrichment
  18. 2026-07-21 17:20 UTCEG score recompute
  19. 2026-07-21 17:20 UTCVendor advisory
  20. 2026-07-21 17:20 UTCGHSA enrichment
  21. 2026-07-21 15:24 UTCEPSS rescore
  22. 2026-07-21 15:24 UTCEPSS rescore
  23. 2026-07-21 14:37 UTCCISA KEV update
  24. 2026-07-21 13:05 UTCVendor advisory
  25. 2026-07-21 13:05 UTCGHSA enrichment
  26. 2026-07-21 08:50 UTCVendor advisory
  27. 2026-07-21 08:50 UTCGHSA enrichment
  28. 2026-07-21 04:35 UTCVendor advisory
  29. 2026-07-21 04:34 UTCGHSA enrichment
  30. 2026-07-21 00:20 UTCVendor advisory
  31. 2026-07-21 00:20 UTCGHSA enrichment
  32. 2026-07-20 20:06 UTCEG score recompute
  33. 2026-07-20 20:06 UTCVendor advisory
  34. 2026-07-20 20:06 UTCGHSA enrichment
  35. 2026-07-20 17:07 UTCEPSS rescore
  36. 2026-07-20 15:51 UTCVendor advisory
  37. 2026-07-20 15:51 UTCGHSA enrichment
  38. 2026-07-20 11:37 UTCVendor advisory
  39. 2026-07-20 11:37 UTCGHSA enrichment
  40. 2026-07-20 07:22 UTCVendor advisory
  41. 2026-07-20 07:22 UTCGHSA enrichment
  42. 2026-07-20 03:08 UTCVendor advisory
  43. 2026-07-20 03:07 UTCGHSA enrichment
  44. 2026-07-19 22:53 UTCVendor advisory
  45. 2026-07-19 22:53 UTCGHSA enrichment
  46. 2026-07-19 18:39 UTCVendor advisory
  47. 2026-07-19 18:39 UTCGHSA enrichment
  48. 2026-07-19 14:23 UTCVendor advisory
  49. 2026-07-19 14:23 UTCGHSA enrichment
  50. 2026-07-19 10:09 UTCVendor advisory
  51. 2026-07-19 10:09 UTCGHSA enrichment
  52. 2026-07-19 05:54 UTCEG score recompute
  53. 2026-07-19 05:54 UTCVendor advisory
  54. 2026-07-19 05:54 UTCGHSA enrichment
  55. 2026-07-19 02:28 UTCEPSS rescore
  56. 2026-07-19 02:28 UTCEPSS rescore
  57. 2026-07-19 01:39 UTCVendor advisory
  58. 2026-07-19 01:39 UTCGHSA enrichment
  59. 2026-07-18 21:25 UTCVendor advisory
  60. 2026-07-18 21:25 UTCGHSA enrichment
  61. 2026-07-18 17:10 UTCVendor advisory
  62. 2026-07-18 17:10 UTCGHSA enrichment
  63. 2026-07-18 12:55 UTCEG score recompute
  64. 2026-07-18 12:55 UTCVendor advisory
  65. 2026-07-18 12:55 UTCGHSA enrichment
  66. 2026-07-18 10:04 UTCEPSS rescore
  67. 2026-07-18 10:04 UTCEPSS rescore
  68. 2026-07-18 08:40 UTCVendor advisory
  69. 2026-07-18 08:40 UTCGHSA enrichment
  70. 2026-07-18 04:26 UTCVendor advisory
  71. 2026-07-18 04:26 UTCGHSA enrichment
  72. 2026-07-18 00:12 UTCVendor advisory
  73. 2026-07-18 00:12 UTCGHSA enrichment
  74. 2026-07-17 19:56 UTCVendor advisory
  75. 2026-07-17 19:56 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-27363
    First seen Jul 23, 2025

    Integer overflow in FreeType software, which also affects Chrome

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

Frequently asked(6)

What is CVE-2025-27363?
CVE-2025-27363 is a critical vulnerability 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 CVE-2025-27363 disclosed?
CVE-2025-27363 was first published in the National Vulnerability Database on March 11, 2025, with the most recent update on April 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 patching attention.
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.
Which products are affected by CVE-2025-27363?
CVE-2025-27363 affects FreeType FreeType. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-27363?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-27363, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.