EUVD-2026-30382
GHSA-j5qm-c5w8-5g85
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Network-delivered via crafted HTML, no privileges needed, mandatory user navigation; write-only memory corruption produces limited integrity impact with no confirmed confidentiality or availability consequence.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionCVE.org
Integer overflow in ANGLE in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Integer overflow in ANGLE, Chrome's graphics translation layer on Windows, enables out-of-bounds memory writes when processing crafted HTML pages in versions prior to 148.0.7778.168. The flaw is scoped to the Windows-specific ANGLE DirectX backend and requires a user to visit an attacker-controlled page, limiting automated exploitation. No public exploit code has been identified at time of analysis, and EPSS places exploitation probability at 0.03% - corroborated by the SSVC assessment of no current exploitation and non-automatable attack path.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Chrome's open-source graphics abstraction layer that translates OpenGL ES API calls to platform-native APIs - on Windows this means DirectX. An integer overflow in this subsystem corrupts memory-size calculations during graphics operations, producing an out-of-bounds write in the ANGLE rendering pipeline. The CVE description cites CWE-472 ('External Control of Assumed-Immutable Web Parameter'), which does not cleanly align with an integer overflow root cause; CWE-190 (Integer Overflow or Wraparound) or CWE-787 (Out-of-bounds Write) would be more technically precise - this appears to be a tagging inconsistency in the source data. The CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) confirms all Chrome versions prior to 148.0.7778.168 on Windows as affected. Tags referencing Red Hat and SUSE suggest downstream Linux distribution advisories exist, though the CVE description explicitly scopes the vulnerability to Windows.
RemediationAI
Update Google Chrome on all Windows systems to version 148.0.7778.168 or later, which is the vendor-released fix per the Chrome Stable Channel Update advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html. Chrome updates automatically for most consumer installations; enterprise administrators should push the update via Google Chrome Enterprise Bundle or group policy and verify the deployed version via chrome://version. For organizations unable to patch immediately, enforcing web content filtering to block access to untrusted or unknown domains reduces exposure, though this cannot prevent exploitation via compromised legitimate sites and carries usability trade-offs. Disabling hardware-accelerated graphics (chrome://settings → System → Use hardware acceleration when available) would remove the ANGLE rendering path entirely as a compensating control, at the cost of degraded rendering performance and increased CPU usage.
Same 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