{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-7341", "assignerOrgId": "ebfee0ef-53dd-4cf3-9e2a-08a5bd7a7e28", "state": "PUBLISHED", "assignerShortName": "Chrome", "dateReserved": "2026-04-28T20:02:37.079Z", "datePublished": "2026-04-28T22:36:07.714Z", "dateUpdated": "2026-04-28T22:36:07.714Z"}, "containers": {"cna": {"affected": [{"vendor": "Google", "product": "Chrome", "versions": [{"version": "147.0.7727.138", "status": "affected", "lessThan": "147.0.7727.138", "versionType": "custom"}]}], "descriptions": [{"lang": "en", "value": "Use after free in WebRTC in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)"}], "problemTypes": [{"descriptions": [{"lang": "en", "description": "Use after free", "cweId": "CWE-416"}]}], "providerMetadata": {"orgId": "ebfee0ef-53dd-4cf3-9e2a-08a5bd7a7e28", "shortName": "Chrome", "dateUpdated": "2026-04-28T22:36:07.714Z"}, "references": [{"url": "https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html"}, {"url": "https://issues.chromium.org/issues/504586599"}]}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "Use after free in WebRTC in Google Chrome prior to 147.0.7727.138 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)"}], "id": "CVE-2026-7341", "lastModified": "2026-04-28T23:16:21.690", "metrics": {}, "published": "2026-04-28T23:16:21.690", "references": [{"source": "chrome-cve-admin@google.com", "url": "https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html"}, {"source": "chrome-cve-admin@google.com", "url": "https://issues.chromium.org/issues/504586599"}], "sourceIdentifier": "chrome-cve-admin@google.com", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-416"}], "source": "chrome-cve-admin@google.com", "type": "Primary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "147.0.7727.138"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "Chrome", "source": "cna", "vendor": "Google"}, "product": "chrome", "vendor": "google"}], "analysis": {"en": {"generated_at": "2026-04-29T02:07:40.738444+00:00", "value": {"mitigation_remediation": ["Upgrade Google Chrome to version 147.0.7727.138 or later.", "If an immediate browser update is not possible, disable WebRTC by navigating to chrome://flags and setting \"Turn off WebRTC\" or \"WebRTC IP handling policy\" to \"Disable\".", "Add content\u2011security\u2011policy restrictions to prevent execution of untrusted scripts from untrusted domains."], "summary": {"action": "Immediate Patch", "impact": "Remote Code Execution via use-after-free in WebRTC"}, "threat_synthesis": {"affected_systems": "The flaw affects all Google Chrome releases prior to version 147.0.7727.138. Users running these earlier versions are susceptible, regardless of operating system, as the issue resides in the core WebRTC implementation bundled with the browser. Updated releases of Chrome starting with 147.0.7727.138 contain the necessary patch.", "description_and_impact": "A use-after-free flaw in Google Chrome\u2019s WebRTC component allows a remote attacker to run arbitrary code inside the browser\u2019s sandbox when a victim opens a specially crafted HTML page. Due to improper memory handling, the attacker can abuse the freed object to execute malicious instructions, compromising confidentiality, integrity, and potentially enabling privilege escalation within the browser if the sandbox is broken. The vulnerability is identified as CWE-416 and carries a high severity rating from Chromium\u2019s security team.", "risk_and_exploitability": "The EPSS score is not available and the vulnerability is not listed on the CISA KEV, but the high severity and the ability to trigger it via a remote HTML payload make the risk substantial. An attacker can embed malicious code in a web page that will be served to users who browse the site, executing the exploit without any interaction beyond page load. The primary attack vector is remote, through malicious or compromised websites that deliver the crafted payload to a vulnerable Chrome user."}}}}, "created": "2026-04-29T00:30:15.864297+00:00", "title": "Use-After-Free in Chrome WebRTC Enabling Remote Code Execution", "updated": "2026-04-29T02:15:47.407657+00:00", "vendors": ["google", "google$PRODUCT$chrome"]}