Skip to content
major vulnerability· requires attention

Affects Google Chrome, a ubiquitous browser; origin-policy bypass could enable widespread data theft and session compromise across organizations.

Web

CVE-2026-91732

8.1
High
EPSS 0.26%Patch available

Chrome AppManifest auth bypass allows same-origin policy bypass via crafted HTML

exploited
No known exploitation not in CISA KEV as of our last sync
fix
Patch available see the advisory in the references
likelihood
EPSS 0.26%top 83% of scored CVEs
Published 15 Sept 2026Analysed here 18 Sept 2026
common questions

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. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.

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.

executive summary
technical analysis
affected
Google Chrome prior to 153.0.8010.47
impact

An attacker (with a compromised renderer + social engineering) can bypass web-origin policy to access/exfiltrate data, hijack sessions, or perform unauthorized actions.

action required

Patch when possible

affected versions
Google Chrome
  • 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.

cisa ssvc

exploitation
none
automatable
no
technical impact
partial

Assessed by CISA 18 Sept 2026 (SSVC 2.0.3).

timeline

  1. 15 Sept 2026Published
  2. 18 Sept 2026CISA SSVC assessment: exploitation none · 3 days later
  3. 18 Sept 2026CVE record last updated · same day later
  4. 18 Sept 2026Analysed by vulneraibility.com · same day later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved