CVE-2021-38003

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Chrome and other Chromium browsers. For every flaw being used in attacks, see Exploited flaws; for Google’s, see Google flaws being used in attacks.

CVE-2021-38003 is a security flaw in Chrome and other Chromium browsers, the JavaScript engine inside Chrome, Edge, Brave, Opera and other Chromium browsers. A booby-trapped web page can corrupt memory in Chrome and other Chromium browsers, which attackers use to take it over. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 3 Nov 2021.[1]

Chrome and other Chromium browsers is in things households have, such as phones, computers, browsers and everyday apps, so the fix matters at home as much as at work. Fixed in version 95.0.4638.69 of Chrome.

Description

CISA calls it a memory corruption in Google Chromium V8. In its words: “Google Chromium V8 Engine has a bug in JSON.stringify, where the internal TheHole value can leak to script code, causing memory corruption. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.”[1]

The underlying weakness is heap buffer overflow (CWE-122), CWE-755, in MITRE’s list of common software weaknesses.[2]

It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record lists one fixed version: everything before it is affected.[2]

ProductFixed in
Chrome95.0.4638.69

Every device with Chrome and other Chromium browsers needs the update.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 3 Nov 2021. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 17 Nov 2021 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 39%. That’s in the top 2% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Google has published a fix or advice.[3] CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Update Chrome and other Chromium browsers now.Chrome updates itself, but only finishes when you restart it: open the menu, choose Help, then About Google Chrome, and click Relaunch. Edge, Brave, Opera and Vivaldi need the same. Then turn on automatic updates, so the next fix arrives on its own.
  2. Check you’re on 95.0.4638.69 or later.Fixed in version 95.0.4638.69 of Chrome. Anything older is what attackers are going after.
  3. If there’s no update, stop using it.CISA’s advice when a flaw being used in attacks has no fix is to stop using the product until it does.

Timeline

DateEvent
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2]
FIRST puts the odds of it being used in attacks in the next 30 days at 39%.[4]

See also

Other Chrome and other Chromium browsers flaws

Other heap buffer overflow flaws

  • CVE-2026-94127, F5 BIG-IP APM: heap-based buffer overflow ·
  • CVE-2025-25249, Fortinet products: heap-based buffer overflow ·
  • CVE-2026-85880, Microsoft Windows: heap-based buffer overflow ·
  • CVE-2025-32706, Microsoft Windows: common log file system (CLFS) driver heap-based buffer overflow ·
  • CVE-2025-24993, Microsoft Windows: NTFS heap-based buffer overflow ·

Added the same day

  • CVE-2021-42258, BQE BillQuick Web Suite: SQL injection ·
  • CVE-2021-42013, Apache HTTP Server: path traversal ·
  • CVE-2021-41773, Apache HTTP Server: path traversal ·
  • CVE-2021-40539, Zoho ManageEngine: aDSelfService plus authentication bypass ·
  • CVE-2021-40444, Microsoft MSHTML: remote code execution ·

Every Google flaw on CISA’s list · Everything added in November 2021

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Google Chromium V8 Memory Corruption Vulnerability”. Known Exploited Vulnerabilities Catalog, added 3 Nov 2021.
  2. ^ National Institute of Standards and Technology. “CVE-2021-38003 Detail”. National Vulnerability Database, published 23 Nov 2021.
  3. ^ Google. Advisories and fixes: chromereleases.googleblog.com, lists.fedoraproject.org.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.386, percentile 98.6, 31 Oct 2026.
  5. CVE Program. “CVE-2021-38003”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.