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 WebRTC

IdentifiersCVE-2025-10501CWE-416· Use After Free

CVE-2025-10501 is a high-severity use-after-free vulnerability in the WebRTC component of Google Chrome. According to the provided content, the flaw affects Chrome versions prior to 140.0.7339.185 on Linux and prior to 140.0.7339.185/.186 on Windows and macOS. The vulnerability can be triggered by a remote attacker via a crafted HTML page, including crafted HTML/JavaScript that manipulates WebRTC state transitions, causing WebRTC to continue using memory after it has been freed. This results in heap corruption and creates conditions for further exploitation. The issue was reported by sherkito on 2025-08-23 and is rated High severity by Chromium.

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 cause heap corruption in the browser process and may lead to arbitrary code execution within the browser sandbox. The provided content also states exploitation may crash the browser, resulting in denial of service. Overall impact is high because the flaw is remotely triggerable through malicious web content and can compromise browser integrity and availability.

Mitigation

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

The provided content indicates no specific workaround or configuration-based mitigation is available. The primary mitigation is to update affected browsers as soon as possible. Where immediate patching is not possible, reducing exposure to untrusted websites may lower risk, but the content does not provide an official mitigation beyond upgrading.

Remediation

Patch, then assume compromise.

Update Google Chrome to a fixed version. The provided content states the vulnerability was fixed in Chrome Stable Channel version 140.0.7339.185/.186, specifically 140.0.7339.185 for Linux and 140.0.7339.185/.186 for Windows and macOS, or later. For downstream Chromium-based products referenced in the content, apply the vendor-provided updates; for example, Palo Alto Networks advises upgrading Prisma Browser to version 141.6.4.55 or later.
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 activity5

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