Google Chrome
Use after free in Passwords in Google Chrome prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
First public PoC
3.1 daysafter publication · 15 Nov 2026
Public PoCs11 on GitHub
CVSS9.6critical · 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
- >= 157.0.8103.78, < 157.0.8103.78
Fixed in 157.0.8103.78
Mitigation
Upgrade Chrome to 157.0.8103.78 or later.
Timeline
Days relative to CVE publicationFirst public PoC 3.1 days after publication; not in CISA KEV. First PoC: abraxas/chrome-autosignin-toast-uaf (created 15 Nov 2026, found by us: 15 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| abraxas/chrome-autosignin-toast-uaf | 15 Nov 2026 +3.1 d | 15 Nov 2026 | 0 | PoC via PoC Index
Flags · score 25
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.