CVE-2026-17869
Chrome WebXR out-of-bounds memory read via crafted page (pre-151.0.7922.72).
Is CVE-2026-17869 being exploited?
Not confirmed. CVE-2026-17869 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-17869?
CVE-2026-17869 is rated High with a CVSS score of 8.1. 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-17869?
Yes. A fix has been recorded for CVE-2026-17869. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17869 affect?
CVE-2026-17869 affects Google Chrome <151.0.7922.72, Potentially Chromium-based browsers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17869?
Upgrade Chrome to 151.0.7922.72+ and restrict untrusted WebXR content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can perform out-of-bounds memory reads via WebXR, risking exposure of sensitive in-process data (tokens, cookies, secrets).
Patch when possible
- 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.