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

Out-of-bounds Read in Video in Google Chrome on ChromeOS

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

CVE-2026-12026 is a high-severity out-of-bounds read vulnerability in the Video component of Google Chrome on ChromeOS prior to version 149.0.7827.115. According to the provided advisory, a remote attacker who had already compromised the renderer process could trigger the flaw via a crafted HTML page, causing Chrome to read memory outside the intended bounds. This could expose potentially sensitive information from process memory. The issue is described by Chromium as an out-of-bounds read in Video.

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 disclosure of potentially sensitive information from process memory. The provided context indicates the attacker must already have compromised the renderer process, after which a crafted HTML page can be used to leverage the out-of-bounds read for memory disclosure. This may aid sandbox escape chains, bypass exploit mitigations, or expose data useful for further exploitation.

Mitigation

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

No specific workaround or temporary mitigation is provided in the supplied content. Practical mitigation is to reduce exposure by applying the vendor update promptly, limiting use of untrusted web content until patched, and maintaining Chrome/Chromium sandboxing and least-privilege controls so that renderer compromise is harder to achieve and less useful.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome on ChromeOS to version 149.0.7827.115 or later. Where Chromium packages are used downstream, apply the relevant vendor security updates that incorporate the Chromium 149.0.7827.114/.115 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
GoogleChromeosoperating_system

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 activity

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