Chrome CVE-2025-6191

This vulnerability presents critical real-world risk despite being patched. CVSS 8.8 with AV:N (network/remote) and UI:R (requires user interaction) reflects a dangerous profile; the attack vector is trivial—merely visiting or being redirected to a malicious page. The AC:L (low complexity) and lack of privilege requirements (PR:N) mean exploitation requires no bypass of security controls. CVSS impact ratings (C:H/I:H/A:H) confirm complete system compromise potential. Without EPSS, KEV, or POC data provided, historical patterns for V8 integer overflows suggest active exploitation is probable given the 8.8 severity and user-interaction attack vector. The vulnerability likely qualifies as "high priority" in SSVC terms due to automatable exploitation and total impact. This is NOT a false-positive high-CVSS issue; integer overflows in memory-unsafe code (C++) powering V8 are consistently exploitable.

An attacker crafts a malicious HTML page embedding JavaScript that triggers the integer overflow in V8's memory management. The victim is socially engineered or redirected (via ad network, compromised site, or phishing email) to visit the page. Upon loading, the JavaScript executes, exploiting the integer overflow to allocate a tiny buffer while V8 believes a large allocation occurred. Subsequent operations write beyond buffer bounds, corrupting heap memory. The attacker leverages this to leak sensitive data (passwords, session tokens) from browser memory or execute shellcode if combined with heap spraying techniques. The attack requires only user interaction (visiting a page) and no user privileges; it succeeds regardless of browser security settings because the bug is in V8's core logic. Modern exploit frameworks (e.g., Metasploit, in-the-wild exploits) likely include POCs given the severity and v8 history.