Skip to content
Fencer Vulns
high 8.8

CVE-2021-38003 kev in the critical feed json

Inappropriate implementation in V8 in Google Chrome prior to 95.0.4638.69 allowed a remote attacker to potentially exploit heap corruption…

published 2021-11-23 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-24476

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

Summary

Inappropriate implementation in V8 in Google Chrome prior to 95.0.4638.69 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 95.0.4638.69
  • chromium Debian 14, Debian 13, Debian 12 97.0.4692.71-0.1

debian advisories DEBIAN-CVE-2021-38003

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

ubuntu advisories UBUNTU-CVE-2021-38003

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 95.0.4638.69-1.1
  • nodejs-electron openSUSE Tumbleweed 13.6.2-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 83.0.4254.27-lp153.2.33.1
  • chromium Package Hub 15 SP3, openSUSE Leap 15.3, openSUSE Leap 15.2 95.0.4638.69-bp153.2.40.3

opensuse advisories openSUSE-SU-2024:11604-1openSUSE-SU-2024:11656-1openSUSE-SU-2024:12948-1openSUSE-SU-2022:0110-1openSUSE-SU-2022:0070-1openSUSE-SU-2022:0047-1

  • qt5-qtwebengine Alpine 3.14 5.15.3_git20211112-r1
  • qt5-qtwebengine Alpine 3.23, Alpine 3.22, Alpine 3.21 +6 more 5.15.3_git20211127-r0

alpine advisories ALPINE-CVE-2021-38003

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 5.0.2497.24-1
  • chromium Arch Linux 95.0.4638.69-1

arch linux advisories AVG-2475AVG-2504

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-38003 updated cvss 8.8

chromium-browser: Inappropriate implementation 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. Added to CISA KEV
  4. CISA patch deadline
  5. Published
  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 Memory Corruption 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-10-26
Patched
2021-10-28
Details
project zero tracker

CISA SSVC

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

Exploit prediction

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

Exploits and checks

  • crbug.com https://crbug.com/1263462 referenced PoC, tagged "exploit" by a source, unverified

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
  • CWE-755 Improper Handling of Exceptional Conditions
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.