CVE-2026-14099
Use-after-free in Chrome for iOS enables heap corruption via crafted HTML and UI gestures.
Is CVE-2026-14099 being exploited?
Not confirmed. CVE-2026-14099 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-14099?
CVE-2026-14099 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-14099?
Yes. A fix has been recorded for CVE-2026-14099. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-14099 affect?
CVE-2026-14099 affects Google Chrome for iOS, iOS prior to 150.0.7871.47. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-14099?
Update to latest Chrome for iOS (≥150.0.7871.47).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap corruption could lead to remote code execution or app crash via crafted HTML and specific UI gestures.
Immediate action required
- affected< 150.0.7871.47
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.