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

Insufficient validation of untrusted input in Google Chrome Input

IdentifiersCVE-2026-9124CWE-20· Improper Input Validation

CVE-2026-9124 is a medium-severity vulnerability in the Input component of Google Chrome prior to version 148.0.7778.179. According to the provided content, the flaw is caused by insufficient validation of untrusted input. A remote attacker who has already compromised the renderer process can use a crafted HTML page to trigger the issue and leak cross-origin data. The available information does not identify the specific vulnerable function or code path, and Google indicated that detailed bug information may remain restricted until most users are patched.

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 cross-origin data leakage from the browser security context. While the issue does not by itself provide initial code execution, it weakens origin isolation and can enable an attacker with renderer-process compromise to access sensitive data that should be isolated by the browser's same-origin protections. Depending on victim activity and accessible targets, this could expose session-related information or other sensitive cross-origin content.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted web content, isolating high-risk browsing activity, and applying enterprise controls that restrict access to attacker-controlled sites. Because exploitation requires prior renderer compromise, mitigations that reduce the likelihood of renderer exploitation and enforce rapid browser restarts after updates may lower risk. However, patching is the primary mitigation based on the available information.

Remediation

Patch, then assume compromise.

Update Google Chrome and Chromium-based deployments to version 148.0.7778.179 or later on affected platforms. The provided content indicates the issue affects Google Chrome prior to 148.0.7778.179. Administrators should ensure the browser update has been fully applied and that the browser is restarted so the patched version is running.
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 activity1

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