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

Out-of-bounds read in V8 object lifecycle handling

IdentifiersCVE-2026-7936CWE-664

CVE-2026-7936 is a medium-severity object lifecycle issue in the V8 JavaScript engine in Google Chrome prior to version 148.0.7778.96. According to the provided content, the flaw allows a remote attacker to trigger an out-of-bounds memory read by inducing incorrect object lifetime/state handling via a crafted HTML page. The issue affects Chrome’s Chromium-based codebase and is specifically described as an object lifecycle problem in V8 rather than a generic parser or policy bug.

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.

Start free trial
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 an attacker to cause an out-of-bounds memory read in the browser process through malicious web content. Based on the provided information, the primary impact is unintended disclosure of memory contents accessible through the affected read primitive. The content does not state confirmed code execution or sandbox escape for this specific CVE.

Mitigation

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

Apply the Chrome 148 stable-channel update immediately. Until patching is completed, reduce exposure by limiting use of untrusted websites and web content, and prioritize updates for internet-exposed user endpoints running Chromium-based browsers. No specific workaround beyond updating is provided in the supplied content.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 148.0.7778.96 or later on affected platforms. Because the issue is in Chromium/V8, corresponding updates should also be applied to Chromium-derived browsers once vendor fixes are 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.

ACTIVITY FEED

Recent activity

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

3 SOURCESView more in app
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.
Start free trial
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.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-7936
NVD
nvd.nist.gov/vuln/detail/CVE-2026-7936
MITRE CWE · CWE-664
cwe.mitre.org
Vendor Advisory
chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html
Issue Tracking
issues.chromium.org/issues/490485402