Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Network delivery via crafted page; AC:H reflects required UI gestures and timing constraints; C:H for arbitrary process memory read; no integrity or availability impact applies.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds read in FileSystem in Google Chrome on Mac prior to 148.0.7778.168 allowed a remote attacker who convinced a user to engage in specific UI gestures to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Out-of-bounds read in the FileSystem component of Google Chrome on macOS (prior to 148.0.7778.168) exposes process memory contents to a remote attacker via a crafted HTML page. Exploitation requires high attack complexity and a user to perform specific UI gestures, substantially constraining opportunistic mass exploitation. No public exploit code has been identified and EPSS sits at the 8th percentile; CISA has not listed this in KEV, and SSVC classifies exploitation status as none.
Technical ContextAI
The vulnerability is rooted in CWE-125 (Out-of-bounds Read) within Chrome's FileSystem API implementation on macOS. The FileSystem component reads memory beyond the bounds of an allocated buffer, allowing adjacent process memory to be surfaced to an attacker-controlled page. The macOS-specific scope (confirmed by the CVE description) suggests the flaw is tied to platform-specific FileSystem API bindings or memory layout behavior unique to macOS Chrome builds. The affected product is identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all Chrome versions prior to the fix, and the underlying defect is tracked as Chromium issue 497095799. The tags referencing 'Buffer Overflow' alongside CWE-125 indicate the read may be triggered by a boundary condition in buffer handling within the FileSystem subsystem.
RemediationAI
Upgrade Google Chrome on macOS to version 148.0.7778.168 or later, as detailed in the Chrome stable channel update advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html. Chrome's built-in auto-update mechanism will apply this silently for most consumer deployments; enterprise environments using managed Chrome deployments (via Google Admin or MDM) should verify the update has been pushed and confirm the installed version via chrome://version. As a compensating control for environments that cannot immediately update, restrict macOS Chrome users from visiting untrusted or external web content, and enforce Chrome's Enhanced Safe Browsing policy to reduce exposure to crafted pages - note these controls reduce but do not eliminate risk and may impact browsing functionality. No workaround eliminates the underlying flaw; patching to 148.0.7778.168 is the only definitive fix.
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30458
GHSA-h69r-vw7v-6c65