Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Integer overflow in V8 in Google Chrome

IdentifiersCVE-2025-10892CWE-190· Integer Overflow or Wraparound

CVE-2025-10892 is a high-severity integer overflow vulnerability in the V8 JavaScript engine used by Google Chrome. It affects Chrome versions prior to 140.0.7339.207, with Windows and Mac patched in 140.0.7339.207/.208 and Linux patched in 140.0.7339.207 according to the provided content. The flaw can be triggered when crafted HTML and JavaScript cause an integer overflow in V8, leading to incorrect size or allocation calculations and subsequent heap corruption. The available content does not identify the exact vulnerable function, but it consistently describes the bug as an integer overflow in V8 that can be reached through a malicious web page.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause heap corruption in the Chrome browser process and may allow arbitrary code execution. The provided content states that a remote attacker could potentially achieve complete compromise of the vulnerable system by luring a victim to open a specially crafted web page.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is provided in the supplied content. If immediate patching is not possible, reduce exposure by limiting access to untrusted websites and untrusted active web content, but the primary mitigation is to upgrade to a patched version as soon as possible.

Remediation

Patch, then assume compromise.

Update Google Chrome to a fixed version. Based on the provided content, the vulnerability was patched in Chrome 140.0.7339.207, with Windows and Mac receiving 140.0.7339.207/.208 and Linux receiving 140.0.7339.207. Apply the latest vendor-provided Chrome update from Google. For downstream Chromium-based products, apply the vendor-specific fixed release where available.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.