Skip to main content
Mallory
HighVulnerability

CVE-2020-6453: Heap Corruption in V8 (Google Chrome < 80.0.3987.162)

Published Jun 3, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS0.91%61st percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Google
IdentifiersCVE-2020-6453CWE-119

CVE-2020-6453 is a vulnerability in the V8 JavaScript engine in Google Chrome prior to version 80.0.3987.162. The issue arises from an inappropriate implementation that allows a remote attacker to trigger heap corruption by enticing a user to visit a specially crafted HTML page. The vulnerability is likely due to improper memory handling in V8, which could lead to memory corruption when processing malicious JavaScript.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability could allow a remote attacker to execute arbitrary code in the context of the browser, potentially leading to full compromise of the affected system if chained with a sandbox escape. The attacker would only need to convince a user to visit a malicious web page.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, users can disable JavaScript or use browser security extensions to limit the execution of untrusted scripts. Restricting access to untrusted websites and employing endpoint security solutions may also reduce the risk of exploitation until the browser is updated.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 80.0.3987.162 or later, which contains the fix for this vulnerability. Users and administrators should ensure automatic updates are enabled to receive security patches promptly.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2020-6453 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-6453?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2020-6453.
Is there a patch for CVE-2020-6453?
Upgrade Google Chrome to version 80.0.3987.162 or later, which contains the fix for this vulnerability. Users and administrators should ensure automatic updates are enabled to receive security patches promptly.
What products are affected by CVE-2020-6453?
Google Chrome.
How severe is CVE-2020-6453?
CVE-2020-6453 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.91% (61st percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.