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

Out-of-bounds memory access in V8 in Google Chrome

IdentifiersCVE-2026-7902CWE-125· Out-of-bounds Read

CVE-2026-7902 is a high-severity out-of-bounds memory access vulnerability in the V8 JavaScript engine used by Google Chrome. According to the provided content, affected versions are Google Chrome prior to 148.0.7778.96. The issue can be triggered remotely via a crafted HTML page, causing V8 to perform memory access outside intended bounds. The vendor states that successful exploitation could allow arbitrary code execution inside the Chrome sandbox.

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 allows a remote attacker to achieve arbitrary code execution within the Chrome renderer sandbox by luring a target to a maliciously crafted HTML page. This creates a drive-by exploitation path from web content and can result in compromise of the sandboxed renderer process, though the provided content does not indicate a sandbox escape or direct system-level code execution.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting use of untrusted websites and limiting access to potentially malicious HTML content, since exploitation is described as occurring via a crafted web page. Standard browser hardening measures such as minimizing unnecessary browsing from sensitive environments may reduce risk, but the primary mitigation is prompt upgrade to the fixed Chrome release.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 148.0.7778.96 or later on Linux, and to 148.0.7778.96/97 or later on Windows and Mac, as referenced in the provided content. Applying the vendor-supplied Chrome 148 stable-channel update remediates this vulnerability.
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.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

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 signatures

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 activity1

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