NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🛡️
Not in CISA KEV
MEDIUM severity

CVE-2020-16040 — Chrome

MEDIUM

CVE-2020-16040 is a medium-severity (CVSS 6.5) Improper Input Validation vulnerability. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published
Updated
Affected
1 product
Patched
See advisory
Exploits
4 known
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
99.6%probability of exploitation in next 30 days
Very High Risk0.00%
Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk
67.8%78.5%89.3%100.0%75.5%99.6%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Description

Insufficient data validation in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Affected Products

1 product · 1 configurations
Application
chromegoogle
< 87.0.4280.88
range
Exploits & PoCs
4

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-49745remotemultiple

Google Chrome 86.0.4240 V8 - Remote Code Execution

by r4j0x00 · Apr 6, 2021

Detection & mitigation playbook

Vulnerability
  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    No fixed release is recorded for CVE-2020-16040 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Insufficient data validation in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
O3 Security · Impact-Aware SCA

Is CVE-2020-16040 in your dependencies?

Find it across your dependency tree, including transitive dependencies.

CVE-2020-16040: Chrome (Medium 6.5)