Affects Google Chrome, a ubiquitous browser; origin-policy bypass could enable widespread data theft and session compromise across organizations.
CVE-2026-91732
Chrome AppManifest auth bypass allows same-origin policy bypass via crafted HTML
Is CVE-2026-91732 being exploited?
Not confirmed. CVE-2026-91732 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.
How severe is CVE-2026-91732?
CVE-2026-91732 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-91732?
Yes. A fix has been recorded for CVE-2026-91732. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91732 affect?
CVE-2026-91732 affects Google Chrome prior to 153.0.8010.47. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91732?
Update Chrome to 153.0.8010.47 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker (with a compromised renderer + social engineering) can bypass web-origin policy to access/exfiltrate data, hijack sessions, or perform unauthorized actions.
Patch when possible
- affected< 153.0.8010.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.