Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page with no auth (AV:N/PR:N) but victim must open it (UI:R); code runs only in the renderer sandbox so scope unchanged (S:U) with high C/I/A within the component.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds write in Fonts in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Renderer-sandboxed remote code execution in Google Chrome's Fonts component (versions prior to 148.0.7778.168) lets a remote attacker run arbitrary code inside the renderer sandbox when a victim opens a crafted HTML page. Rated High by Chromium and CVSS 8.8, the flaw is a CWE-787 out-of-bounds write reported internally by the Chrome team. There is no public exploit identified at time of analysis, and EPSS is very low (0.04%, 11th percentile), consistent with the CISA SSVC assessment of no known exploitation.
Technical ContextAI
The vulnerability lives in Chrome's font-handling code, part of the Blink rendering engine that parses and rasterizes font data (e.g., glyph tables from web fonts or system fonts referenced by a page). The root cause is CWE-787, an out-of-bounds write, where malformed font structures cause the parser to write past an allocated buffer, corrupting adjacent heap memory. Because font parsing runs inside the renderer process, successful memory corruption yields code execution confined to that sandboxed process rather than the host OS. The single affected product per CPE is cpe:2.3:a:google:chrome (all versions below the fix), and the Blink font stack is shared across Chromium-based downstreams.
RemediationAI
Vendor-released patch: update Google Chrome to 148.0.7778.168 or later (Stable channel), per the Chrome release blog https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html; restart the browser to apply the update since Chrome patches only take effect after relaunch. For managed fleets, push the update via enterprise policy and verify the version at chrome://settings/help. Chromium-based and repackaged builds (e.g., Red Hat, SUSE) should be upgraded to their vendor release that incorporates the fixed Chromium version. As interim compensating controls until updates roll out, reduce exposure to untrusted pages by enabling Enhanced Safe Browsing and, in high-security environments, deploying site isolation and restricting web-font/JavaScript execution on untrusted origins - noting the trade-off that aggressively blocking web fonts or scripting degrades rendering and breaks many legitimate sites.
Same weakness CWE-787 – Out-of-bounds Write
View allVendor StatusVendor
SUSE
Severity: High| 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-30437
GHSA-7m72-mq6q-p26x