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

Use-after-free in Google Chrome Permissions on Android

IdentifiersCVE-2026-6315CWE-416· Use After Free

CVE-2026-6315 is a high-severity use-after-free vulnerability in the Permissions component of Google Chrome. The issue affects Google Chrome on Android prior to version 147.0.7727.101, and the supporting content indicates the vulnerable Permissions code is shared across Chromium-based desktop builds that were also patched in the same release. The flaw arises from a memory object in the Permissions component being freed while a stale reference is retained and later dereferenced, creating a classic use-after-free condition. A remote attacker can trigger the bug using a crafted HTML page, but successful exploitation requires convincing the victim to perform specific UI gestures; page load alone is not sufficient. The exact gestures are not publicly documented. If the freed memory is reoccupied with attacker-controlled data through heap manipulation, the condition can be turned into arbitrary code execution in the Chrome browser process.

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 result in arbitrary code execution in the Chrome browser process. Based on the provided CVSS v3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H and the supporting content, the vulnerability can have high impact on confidentiality, integrity, and availability. In practical terms, exploitation could allow an attacker to run code within the context of the browser, access or manipulate data available to that process, and potentially crash the browser or otherwise disrupt service.

Mitigation

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

Until patching is complete, reduce exposure by limiting use of untrusted websites on affected Chrome for Android installations and minimizing opportunities for users to interact with unexpected permission-related prompts or other attacker-driven UI flows. Enterprise defenders can prioritize rapid rollout of the fixed Chrome stable versions and, where feasible, restrict or monitor browsing to untrusted content on vulnerable devices. No specific vendor-provided workaround beyond updating is present in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to a fixed version. The content states Google addressed the issue on April 15, 2026 in Chrome 147.0.7727.101 for Android and Linux, and 147.0.7727.101/.102 for Windows and macOS. Any Chrome version prior to 147.0.7727.101 should be treated as vulnerable. Apply vendor updates through Google Play on Android and the corresponding stable channel updates on desktop platforms.
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.