Affects the widely used Google Chrome browser; heap corruption via WebRTC could lead to remote code execution or browser compromise across enterprise endpoints.
CVE-2026-17884
Heap-corruption in Chrome WebRTC allows remote exploitation via crafted HTML.
Is CVE-2026-17884 being exploited?
Not confirmed. CVE-2026-17884 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.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-17884?
CVE-2026-17884 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-17884?
Yes. A fix has been recorded for CVE-2026-17884. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17884 affect?
CVE-2026-17884 affects Google Chrome <151.0.7922.72 (WebRTC), Potentially other Chromium-based browsers pending vendor updates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17884?
Update Chrome to 151.0.7922.72 or later; restrict untrusted WebRTC pages until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap corruption in WebRTC can enable remote code execution or full browser compromise via a crafted webpage.
Immediate action required
- affected< 151.0.7922.72
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.