Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
6 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacker to perform a sandbox escape via a malicious file. (Chromium security severity: High) https://nvd.nist.gov/vuln/detail/CVE-2025-2783 https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop25.html https://issues.chromium.org/issues/405143032
Recommended action: Upgrade to 134.3.90 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
CVE-2022-0609: Use after free in Animation - https://chromereleases.googleblog.com/2022/02/stable-channel-update-for-desktop14.html - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0609 Google is aware of reports that exploits for CVE-2022-0609 exist in the wild. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are unknown but an exploit is available. There is currently little other public information on the issue other than it has been flagged as High severity.
Recommended action: Upgrade to 98.1.210 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
CVE-2020-16009: Inappropriate implementation in V8 - https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop.html - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16009 Google is aware of reports that exploits for CVE-2020-16009 exist in the wild. Allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. There is currently little to no public information on the issue other than it has been flagged as High severity.
Recommended action: Upgrade to 86.0.241 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
CVE-2020-16017: Use after free in site isolation - https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop11.html - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16017 Google is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild. There is currently little to no public information on the issue other than it has been flagged as High severity.
Recommended action: Upgrade to 86.0.241 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
High CVE-2020-16013: Inappropriate implementation in V8. - https://chromereleases.googleblog.com/2020/11/stable-channel-update-for-desktop11.html - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16013 Google is aware of reports that exploits for CVE-2020-16013 and CVE-2020-16017 exist in the wild. There is currently little to no public information on the issue other than it has been flagged as High severity.
Recommended action: Upgrade to 86.0.241 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact A memory corruption bug(Heap overflow) in the FreeType font rendering library. This can be exploited by attackers to execute arbitrary code by using specially crafted fonts with embedded PNG images . As per https://www.secpod.com/blog/chrome-zero-day-under-active-exploitation-patch-now/ Google is aware of reports that an exploit for CVE-2020-15999 exists in the wild. Patches Upgrade to 85.3.130 or higher References - https://www.secpod.com/blog/chrome-zero-day-under-active-exploitation-patch-now/ - https://www.zdnet.com/article/google-releases-chrome-security-update-to-patch-actively-exploited-zero-day/ - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15999 - https://magpcss.org/ceforum/viewtopic.php?f=10&t=17942 To review the CEF/Chromium patch see https://bitbucket.org/chromiumembedded/cef/commits/cd6cbe008b127990036945fb75e7c2c1594ab10d
Recommended action: Upgrade to 85.3.130 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.