Automated Threat Modeling

Google Chrome V8 Integer Overflow (CVE-2025-10892): Brief Summary and Technical Review

CVE-2025-10892 is a high-severity integer overflow in Google Chrome's V8 JavaScript engine, patched in version 140.0.7339.207. This brief technical review covers the affected versions, how the flaw works, and Google's security record with V8.

CVE Analysis

7 min read

ZeroPath CVE Analysis
ZeroPath CVE Analysis

2025-09-24

Google Chrome V8 Integer Overflow (CVE-2025-10892): Brief Summary and Technical Review
Experimental AI-Generated Content

This CVE analysis is an experimental publication that is completely AI-generated. The content may contain errors or inaccuracies and is subject to change as more information becomes available. We are continuously refining our process.

If you have feedback, questions, or notice any errors, please reach out to us.

[email protected]

Introduction

A remote attacker could corrupt the heap in Google Chrome just by getting a user to open a malicious web page. The vulnerability, tracked as CVE-2025-10892, is in the V8 JavaScript engine and was patched in Chrome version 140.0.7339.207. Chrome has a huge user base, so a flaw like this has immediate global impact, and both defenders and attackers pay close attention to it.

Technical Information

CVE-2025-10892 is an integer overflow in the V8 JavaScript engine used by Google Chrome. Every version before 140.0.7339.207 has the flaw. An integer overflow happens when an arithmetic operation produces a value larger than the variable can hold, so the value wraps around to zero or to a negative number. In V8, this can lead to incorrect memory allocation or wrong buffer size calculations.

To exploit it, an attacker delivers a specially crafted HTML page with JavaScript that triggers the overflow. The overflow may corrupt the heap, which could let the attacker execute arbitrary code inside the browser process. The vulnerability is classified as CWE-190 (Integer Overflow or Wraparound). The Chromium security team rated it high severity, with a CVSS score of 8.8.

No public code snippets or detailed PoC exist for this issue. Google found the vulnerability internally with Big Sleep, its AI-powered system, and the find is one more sign that automated analysis is taking on a larger share of vulnerability discovery.

Affected Systems and Versions

  • Google Chrome versions prior to 140.0.7339.207 on Linux
  • Google Chrome versions prior to 140.0.7339.207/.208 on Windows and Mac
  • All configurations using the affected V8 engine versions are vulnerable

Vendor Security History

Google Chrome's V8 engine has produced several high-severity vulnerabilities in recent years, including CVE-2025-10585 and CVE-2025-10890. Google has a record of responding quickly to these issues, often releasing patches within days to weeks of discovery. The company also looks for flaws proactively, using fuzzing and AI-driven systems such as Big Sleep. Chrome's update mechanism is reliable and is widely regarded as a model for the industry.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization