Quick answers
- Is CVE-2026-49919 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49919 being exploited in the wild.
- How severe is CVE-2026-49919?
- High severity, with a CVSS score of 7.8, published 8 September 2026.
- Which products and versions are affected?
- FreeType <UNKNOWN>.
- Is there a fix for CVE-2026-49919?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-49919 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49919?
- Check whether you run FreeType at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An integer overflow in the tt_face_colr_blend_layer function of ttcolr.c (part of FreeType's COLR table handling) can be triggered by a maliciously crafted font file. The vulnerability does not require authentication or user interaction beyond opening/processing a malicious font, and operates at a local level. Successful exploitation allows an attacker to achieve local privilege escalation or, depending on context, remote code execution. The Android security bulletin indicates patches are available in AOSP; FreeType upstream should also have addressed this issue.
Affected products
- FreeType FreeType <UNKNOWN>
Timeline
- 2026-09-08: disclosed
- 2026-09-01: advisory: Android Security Bulletin published