# CVE-2026-91732 — Google Chrome

> As of 2026-11-06, CVE-2026-91732 is a LOW-severity vulnerability in Google Chrome, CVSS v3.1 3.1, EPSS 0.2% (18.0th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-91732, most recently “Multiple Vulnerabilities in Microsoft Edge (Chromium) and Visual Studio 2017-2026 - HK GovCERT Alert A26-11-02 (CVE-2026-91732, CVE-2026-118147, CVE-2026-118322)”.

**Last updated:** 2026-09-18

## What is CVE-2026-91732?

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)

The record classifies CVE-2026-91732 under weakness class [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 53 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.1 — LOW (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 18.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-15, last modified 2026-09-18

## Is CVE-2026-91732 being exploited?

Weaponised exploit code for CVE-2026-91732 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

- [trickest/cve](https://github.com/trickest/cve/blob/main/2026/CVE-2026-91732.md) (trickest)

## Affected products and versions

- [Google](https://intel.threadlinqs.com/vendors/google): Chrome

## How to fix CVE-2026-91732

The record marks a vendor fix as available for CVE-2026-91732. Patch reference: [https://issues.chromium.org/issues/511062248](https://issues.chromium.org/issues/511062248). Vendor advisory: [https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0541751186.html](https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0541751186.html). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-91732

1 tracked threat in the Threadlinqs corpus references CVE-2026-91732, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Multiple Vulnerabilities in Microsoft Edge (Chromium) and Visual Studio 2017-2026 - HK GovCERT Alert A26-11-02 (CVE-2026-91732, CVE-2026-118147, CVE-2026-118322)](https://intel.threadlinqs.com/threat/TL-2026-5450) — HIGH · 2026-11-06

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-11-07. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0541751186.html)
- [issues.chromium.org](https://issues.chromium.org/issues/511062248)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-91732
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp