Skip to main content
Public proof of conceptFix available

CVE-2020-6507

A public proof of concept exists; no exploitation attested.

  • Published2020-07-22
  • Fixed in83.0.4103.106
  • WeaknessCWE-20 · CWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Out of bounds write in V8 in Google Chrome prior to 83.0.4103.106 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Timeline

dates in UTC
  1. 2021-04-06Exploit-DB entryExploit-DB

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-6507?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-6507?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Google chrome
BranchAffectedFixed in
83.0< 83.0.4103.10683.0.4103.106

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • chromiumSUSE:Package Hub 15 SP1all versions · fixed in 83.0.4103.106-bp151.3.88.1
  • chromiumopenSUSE:Tumbleweedall versions · fixed in 93.0.4577.82-1.1
  • chromiumopenSUSE:Tumbleweedall versions · fixed in 113.0.5672.92-1.1
  • chromiumopenSUSE:Leap 15.2all versions · fixed in 83.0.4103.116-lp152.2.3.1
  • chromiumopenSUSE:Leap 15.1all versions · fixed in 83.0.4103.106-lp151.2.101.1
  • chromiumDebian:14all versions · fixed in 83.0.4103.106-1
  • chromiumDebian:13all versions · fixed in 83.0.4103.106-1
  • chromiumDebian:12all versions · fixed in 83.0.4103.106-1

20 more package ranges on OSV.dev

Vendor advisories

  • CVE-2020-6507 Red Hat Product Security14 products fixed

    chromium-browser: Out of bounds write in V8

  • RHSA-2020:2643 Red Hat Product Security14 products fixed

    Red Hat Security Advisory: chromium-browser security update

Full record on NVD

Fix

  1. Update Google chrome to 83.0.4103.106
  2. Vendor fix Red Hat Product Security RHSA-2020:2643 · 14 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the update, Chromium must be restarted for the changes to take effect.

Advisories and patches

Detection

read 2026-11-02 22:42 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
EDB-49746
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.18.8read 2026-10-23
  • NVDCVSS 2.06.8read 2026-10-23
  • NVDweakness (CWE)CWE-20, CWE-787read 2026-10-23
  • FIRST EPSSEPSS score19.1 %read 2026-11-02
  • Exploit-DBdetectionread 2026-11-02
  • OSVaffected packages—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2020-07-22
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2020-6507?

Out of bounds write in V8 in Google Chrome prior to 83.0.4103.106 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Is CVE-2020-6507 actively exploited?

Active exploitation of CVE-2020-6507 has not been confirmed. Its EPSS score was 19.1% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-6507?

CVE-2020-6507 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running chromium-browser? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record