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

Integer overflow in Google Chrome V8

IdentifiersCVE-2025-10891CWE-190

CVE-2025-10891 is a high-severity integer overflow vulnerability in the V8 JavaScript engine used by Google Chrome and other Chromium-based browsers. The issue affects Google Chrome prior to 140.0.7339.207/.208 on Windows and Mac and prior to 140.0.7339.207 on Linux. According to the provided content, the flaw is caused by insufficient bounds checking on certain arithmetic operations in V8. When attacker-controlled values exceed the maximum range of the underlying integer type, calculations can wrap and produce incorrect values that are then used in memory allocation or array indexing. This can lead to heap corruption when a victim opens a specially crafted HTML page containing malicious JavaScript. The content states that successful exploitation may allow arbitrary code execution in the context of the browser process.

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 enable arbitrary code execution. The provided content further states that exploitation may result in complete compromise of the vulnerable system, with high confidentiality, integrity, and availability impact.

Mitigation

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

The provided content does not describe a reliable workaround. Primary mitigation is to deploy the vendor patch as soon as possible. Until patching is complete, reduce exposure by limiting use of untrusted websites and untrusted active web content, and applying standard browser hardening controls where operationally feasible, but no specific mitigation short of updating is documented in the provided material.

Remediation

Patch, then assume compromise.

Update Google Chrome to the fixed versions released by Google: 140.0.7339.207/.208 for Windows and Mac, and 140.0.7339.207 for Linux, or later. The content states Google addressed the issue by adding stricter bounds checks to vulnerable arithmetic operations in V8. For downstream Chromium-based products, apply the corresponding vendor-supplied updates that incorporate the Chrome/V8 fixes.
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.