CVE-2020-16027

Description

Insufficient policy enforcement in developer tools in Google Chrome prior to 87.0.4280.66 allowed an attacker who convinced a user to install a malicious extension to obtain potentially sensitive information from the user's disk via a crafted Chrome Extension.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.13%
Vendor Advisory googleblog.com Vendor Advisory crbug.com
Affected: Google Chrome
Published at:
Updated at:

References

Link Tags
https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop_17.html release notes vendor advisory
https://crbug.com/1116444 permissions required vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-16027?
CVE-2020-16027 has been scored as a medium severity vulnerability.
How to fix CVE-2020-16027?
To fix CVE-2020-16027, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-16027 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-16027 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-16027?
CVE-2020-16027 affects Google Chrome.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.