Google Chrome
Google Chromium Out of Bounds Memory Access Vulnerability
Out of bounds memory access in ANGLE in Google Chrome on Mac prior to 143.0.7499.110 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 143.0.7499.110, < 143.0.7499.110
Fixed in 143.0.7499.110
Mitigation
Upgrade Chrome to 143.0.7499.110 or later.
Timeline
Days relative to CVE publicationFirst public PoC 59 days after publication; added to CISA KEV 0 h after publication. First PoC: George0Papasotiriou/CVE-2025-14174-Chrome-Zero-Day (created 10 Feb 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs · 2 informational · 1 suspicious or fake
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| George0Papasotiriou/CVE-2025-14174-Chrome-Zero-Day | 10 Feb 2026 +59 d | 3 | PoC via PoC Index |
Informational 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| typeconfused/CVE-2025-14174-analysis | 4 Jan 2026 +22 d | 4 | Informational · write-up |
| 0xjohnnydev/WebKit-UAF-ANGLE-OOB-Analysis | 13 Jan 2026 +31 d | 115 | Informational · write-up
Flags · score 20
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Satirush/CVE-2025-14174-Poc | 18 Dec 2025 +5.7 d | 10 | Suspicious · score 65
Why suspicious
|
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.