CVE-2020-6492 in the critical feed json
Use after free in ANGLE in Google Chrome prior to 83.0.4103.97 allowed a remote attacker to potentially perform a sandbox escape via a craf…
published 2021-11-02 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-27642
- cvss
- 9.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
Use after free in ANGLE in Google Chrome prior to 83.0.4103.97 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.
Patch / fix
- Google Chrome 83.0.4103.97
- chromium Debian 14, Debian 13, Debian 12 83.0.4103.106-1
debian advisories DEBIAN-CVE-2020-6492
- chromium-browser Ubuntu 16.04 LTS 84.0.4147.105-0ubuntu0.16.04.1
- chromium-browser Ubuntu 18.04 LTS 84.0.4147.105-0ubuntu0.18.04.1
ubuntu advisories UBUNTU-CVE-2020-6492
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- crbug.com/1078375 advisory
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- crbug.com https://crbug.com/1078375 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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
References
-
crbug.com
/1078375
exploit, issue-tracking, patch, third-party-advisory
-
chromereleases.googleblog.com
/2020/06/stable-channel-update-for-desktop.html
third-party-advisory
Sources
- CVE List CVE-2020-6492
- NVD CVE-2020-6492
Fencer Vulns 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.