No. CVE-2020-15999
A Google Chrome FreeType bug is being used in attacks
Yes. Attackers are using this right now.
What to do
Apply the vendor's update. If there is none, stop using it or cut it off from the internet.
- Confirmed in attacks
- Nov 3, 2021
- Product
- Google Chrome FreeType
- Attack likelihood, next 30 days
- 64%
Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.
The official description
Google Chrome uses FreeType, an open-source software library to render fonts, which contains a heap buffer overflow vulnerability in the function Load_SBit_Png when processing PNG images embedded into fonts. This vulnerability is part of an exploit chain with CVE-2020-17087 on Windows and CVE-2020-16010 on Android.
Required action: Apply updates per vendor instructions.
For your tech helper
A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.
Read-only check, change nothing, send nothing anywhere.
Is Google Chrome FreeType (CVE-2020-15999) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2020-15999. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.