Use after free in printing in Google Chrome prior to 86.0.4240.99 allowed a remote attacker to potentially exploit heap corruption via a cr…

published 2020-11-03 6y ago modified 2026-06-17 4mo ago also EUVD-2020-7964

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.1%; EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits: 0; none known

Use after free in printing in Google Chrome prior to 86.0.4240.99 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Patch / fix

fixed in 1

Google Chrome 86.0.4240.99

Is CVE-2020-15993 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.13% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

Google Chrome

Classification

Weakness

CWE-416 Use After Free

Technology feeds

Google Chrome rss critical rss

References

crbug.com /1133983
permissions-required, vendor-advisory
chromereleases.googleblog.com /2020/10/chrome-for-android-update_31.html
release-notes, vendor-advisory

Sources

CVE List CVE-2020-15993
NVD CVE-2020-15993

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.