Skip to content

CVE-2026-91732

8.1 HIGHPublic exploitEPSS 0.25%
  1. Published15 Sept 2026

Description

Missing authorization in AppManifest in Google Chrome prior to 153.0.8010.47 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected products

Google Chrome< 153.0.8010.47

Frequently asked

Is CVE-2026-91732 being actively exploited?

CVE-2026-91732 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.25%.

How severe is CVE-2026-91732?

CVE-2026-91732 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.25% probability of exploitation.

Which products are affected by CVE-2026-91732?

Affected products include Google Chrome.

How do I fix CVE-2026-91732?

Upgrade affected software to a fixed version, for example Google Chrome 153.0.8010.47 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-91732 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.