Google Chrome
Use after free in Input in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
First public PoC
66 daysafter publication · 3 Aug 2026
Public PoCs11 on GitHub
CVSS8.3high · scored by CISA ADP · CWE-416
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Google Chrome
- >= 148.0.7778.216, < 148.0.7778.216
Fixed in 148.0.7778.216
Mitigation
Upgrade Chrome to 148.0.7778.216 or later.
Timeline
Days relative to CVE publicationFirst public PoC 66 days after publication; not in CISA KEV. First PoC: George0Papasotiriou/CVE-2026-9997-VPN-Split-Tunneling-Bypass-via-DHCP-Option-Injection (created 3 Aug 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| George0Papasotiriou/CVE-2026-9997-VPN-Split-Tunneling-Bypass-via-DHCP-Option-Injection | 3 Aug 2026 +66 d | 0 | PoC via PoC Index
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.