CVE-2021-38003
KEVGoogle Chromium V8 Memory Corruption Vulnerability
Description
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.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HPublishedNov 23, 2021
Last modifiedJun 17, 2026
Added to KEVNov 3, 2021
Remediation dueNov 17, 2021
References
- chromereleases.googleblog.com/2021/10/stable-channel-update-for-desktop_28.htmlRelease Notes
- crbug.com/1263462ExploitIssue Tracking
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3W46HRT2UVHWSLZB6JZHQF6JNQWKV744/Release Notes
- debian.org/security/2022/dsa-5046Mailing ListThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-38003US Government Resource
0 recent articles mention this CVE
78
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1805 days
- CVSS
- 8.8 HIGH
- EPSS (30-day exploit probability)
- 38.6% · top 1% of all CVEs
- Weakness
- CWE-755
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.