Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessVictim enables LiveCaption in Chrome
-
DeliveryVisits attacker-controlled site
-
ExploitSite delivers crafted media stream
-
ExecutionLiveCaption parser reads out of bounds
-
PersistAdjacent renderer memory leaked
-
ImpactSensitive data exfiltrated to attacker
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The victim must be running Chrome older than 149.0.7827.53 with the LiveCaption feature actively in use (it is opt-in via Settings → Accessibility → Live Caption and is not enabled by default on most platforms), and must interact with attacker-controlled content - per CVSS UI:R, the user has to visit a page or accept media that delivers the crafted network traffic. No authentication to Chrome or the target site is required (PR:N), and the attack is network-reachable (AV:N), but exploitation is bounded by Chrome's renderer sandbox, so memory disclosure stays within the renderer process unless chained with a sandbox escape. The narrow LiveCaption-enabled prerequisite is the primary limiting factor that reduces the realistic attack surface well below what the 8.8 CVSS suggests. |
| Impact | Signals conflict sharply here: NVD assigns CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/C:H/I:H/A:H), implying network-reachable, low-complexity, high-impact compromise, but Google's own Chromium severity is Low and the CWE is an out-of-bounds READ (typically info disclosure, not RCE), which makes the C:H/I:H/A:H rating look inflated. EPSS at 0.03% (11th percentile) and the absence of CISA KEV listing or any public POC reinforce that real-world risk is currently low. The most likely realistic outcome is bounded memory disclosure from a renderer process, not full code execution, though the vendor's terse description leaves room for uncertainty - verify with Google's Chromium issue 504180386 once it is opened to the public. |
| Exploit ScenarioDerived | A user with LiveCaption enabled visits an attacker-controlled site or loads media from a malicious peer (e.g., over WebRTC or an HLS/MSE stream); the page delivers a crafted media payload that triggers an out-of-bounds read inside the LiveCaption pipeline, leaking adjacent renderer memory back to the attacker via timing or a follow-on primitive. No public POC is identified at time of analysis, and the UI:R requirement means the victim must interact with the malicious content (visit a page or accept a stream). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 05, 2026
Out-of-bounds memory access in Google Chrome's LiveCaption component prior to version 149.0.7827.53 allows a remote attacker to read beyond allocated buffers by delivering crafted network traffic to a user with the feature in use. EPSS is very low (0.03%, 11th percentile) and there is no public exploit identified at time of analysis, though Google's Chromium tracker rated severity Low while NVD's CVSS scored it 8.8 High - a notable disparity worth weighing when prioritizing.
RemediationAI
Vendor-released patch: Google Chrome 149.0.7827.53 - update Chrome via the built-in updater or by restarting the browser, per the Stable Channel announcement at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprise fleets should push the 149.0.7827.53 build through their managed update channel and verify rollout with chrome://version. As a temporary compensating control while patching, administrators can disable LiveCaption via the LiveCaptionEnabled enterprise policy (set to false) to remove the affected code path; the trade-off is loss of in-browser captioning for users who rely on it for accessibility. Chromium-derivative browsers (Edge, Brave, Opera, Vivaldi) should be updated once their corresponding rebased builds ship.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
LiveCaption is Chrome's on-device accessibility feature that transcribes audio from media and call streams in the browser, processing network-delivered audio/media payloads through a parser pipeline. CWE-125 (Out-of-bounds Read) indicates the implementation reads memory outside the bounds of an allocated buffer, typically due to missing length validation on attacker-controlled fields in the media stream. The affected component sits inside the renderer/media stack of Chromium, so exploitation is constrained by Chrome's sandbox unless chained with a sandbox escape.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
Sources disagree (Low–High)AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in LiveCaption in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform out of bounds memory access via malicious network traffic. (Chromium security severity: Low)
Executive ViewAI
Google Chrome's LiveCaption feature contains a memory vulnerability (CVSS 8.8) enabling attackers to extract sensitive data from browser memory through malicious network traffic. Despite the technical severity, zero exploitation probability and absence of public exploits present minimal current risk; however, timely patching remains important to close the gap before threat actors develop attack methodologies.
Apply vendor patch. Interim mitigation: disable LiveCaption feature in Chrome settings (Settings > Accessibility > LiveCaption) until patch is deployed.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome Security Fixes (149.0.7827.53)
View all 72Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-34762
GHSA-5x33-56vh-29gj
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB