Skip to content
Fencer Vulns
high 8.8

CVE-2021-30632 kev in the critical feed json

Out of bounds write in V8 in Google Chrome prior to 93.0.4577.82 allowed a remote attacker to potentially exploit heap corruption via a cra…

published 2021-10-08 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-17552

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
63.2%
EPSS 63.2% chance of exploitation in 30 days, percentile 99.2%
public exploits
0
none known

Summary

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

Patch / fix

cisa required action Apply updates per vendor instructions.

  • Google Chrome 93.0.4577.82
  • chromium Debian 14, Debian 13, Debian 12 93.0.4577.82-1

debian advisories DEBIAN-CVE-2021-30632

  • chromium-browser Ubuntu 18.04 LTS 94.0.4606.71-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2021-30632

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium openSUSE Tumbleweed 93.0.4577.82-1.1
  • nodejs-electron openSUSE Tumbleweed 13.5.0-1.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • opera openSUSE Leap 15.4 NonFree 85.0.4341.28-lp154.2.5.1
  • nodejs-electron Package Hub 15 SP3, openSUSE Leap 15.3 16.0.9-bp153.2.1
  • opera openSUSE Leap 15.3 NonFree, openSUSE Leap 15.2 NonFree 79.0.4143.50-lp153.2.21.1
  • chromium openSUSE Leap 15.2 93.0.4577.82-lp152.2.125.1
  • chromium Package Hub 15 SP3, openSUSE Leap 15.3 93.0.4577.82-bp153.2.28.1

opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:11550-1openSUSE-SU-2024:12948-1openSUSE-SU-2022:0110-1openSUSE-SU-2022:0070-1openSUSE-SU-2021:1330-1

  • chromium Alpine 3.24, Alpine 3.23, Alpine 3.22 +8 more 93.0.4577.82-r0

alpine advisories ALPINE-CVE-2021-30632

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • vivaldi Arch Linux 4.2.2406.44-1
  • chromium Arch Linux 93.0.4577.82-1

arch linux advisories AVG-2337AVG-2379

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-30632 updated cvss 8.8

chromium-browser: Out of bounds write in V8

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Found exploited as a 0-day (Project Zero)
  2. 0-day patched (Project Zero)
  3. Published
  4. Added to CISA KEV
  5. CISA patch deadline
  6. CISA SSVC: exploitation active

Known exploited

Added
5 y ago
Patch by
2021-11-17 (4 y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Google, Chromium V8
CISA name
Google Chromium V8 Out-of-Bounds Write Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Found
2021-09-08
Patched
2021-09-13
Details
project zero root cause analysis

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

63.19% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.