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

Heap Buffer Overflow in Chromecast in Google Chrome

IdentifiersCVE-2026-9123CWE-122· Heap-based Buffer Overflow

CVE-2026-9123 is a heap buffer overflow in the Chromecast component of Google Chrome. According to the provided content, it affects Google Chrome on Android, Linux, and ChromeOS prior to version 148.0.7778.179, and was assigned Chromium security severity Medium. The flaw can be triggered by malicious network traffic and may corrupt heap memory within the Chromecast code path, resulting in arbitrary code execution inside the Chrome sandbox. No additional vulnerable function or root-cause implementation details are provided in the supplied content.

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 allow a local attacker to achieve arbitrary code execution within the Chrome sandbox. The supplied content also indicates the issue may be reachable via malicious network traffic. Based on the available information, impact is therefore limited to code execution in a sandboxed context; no evidence is provided here for sandbox escape, privilege escalation, or direct compromise of the underlying operating system.

Mitigation

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

Until patching is complete, reduce exposure by limiting use of vulnerable Chrome/Chromium builds on affected platforms, restricting untrusted network content and untrusted casting/Chromecast-related workflows where operationally feasible, and applying standard browser hardening controls. Prioritize rapid rollout of the vendor update because no specific configuration-based workaround is provided in the supplied content.

Remediation

Patch, then assume compromise.

Update Google Chrome/Chromium to a fixed release. The provided content states affected versions are prior to 148.0.7778.179; organizations should deploy Chrome/Chromium version 148.0.7778.179 or later, or the corresponding vendor-packaged Chromium security update that includes the fix for CVE-2026-9123. Ensure browsers are restarted after updating so the patched version is active.
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 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 activity3

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