CVE-2026-91732

HIGHNVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
8.1
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-91732(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 10:15 UTCGHSA enrichment
  2. 2026-09-24 21:40 UTCEG score recompute
  3. 2026-09-24 21:40 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 09:03 UTCGHSA enrichment
  6. 2026-09-23 20:28 UTCEG score recompute
  7. 2026-09-23 20:28 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 07:53 UTCGHSA enrichment
  10. 2026-09-22 19:17 UTCEG score recompute
  11. 2026-09-22 19:17 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 06:37 UTCEG score recompute
  14. 2026-09-22 06:37 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 18:02 UTCGHSA enrichment
  17. 2026-09-21 05:25 UTCEG score recompute
  18. 2026-09-21 05:25 UTCGHSA enrichment
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-20 16:48 UTCGHSA enrichment
  21. 2026-09-20 04:13 UTCEG score recompute
  22. 2026-09-20 04:12 UTCGHSA enrichment
  23. 2026-09-19 15:37 UTCGHSA enrichment
  24. 2026-09-19 02:58 UTCEG score recompute
  25. 2026-09-19 02:58 UTCGHSA enrichment
Show 15 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 14:22 UTCGHSA enrichment
  3. 2026-09-18 13:44 UTCEG score recompute
  4. 2026-09-18 13:44 UTCGHSA enrichment
  5. 2026-09-18 11:13 UTCEG score recompute▲ 1.60
  6. 2026-09-18 11:13 UTCGHSA enrichment
  7. 2026-09-18 11:13 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 18:23 UTCGHSA enrichment
  10. 2026-09-16 19:25 UTCEG score recompute
  11. 2026-09-16 19:25 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-15 21:18 UTCNVD update
  14. 2026-09-15 20:43 UTCEG score recompute
  15. 2026-09-15 20:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91732?
CVE-2026-91732 is a high vulnerability published on September 15, 2026. 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)
When was CVE-2026-91732 disclosed?
CVE-2026-91732 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91732 actively exploited?
CVE-2026-91732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.1% of all scored CVEs.
What is the CVSS score of CVE-2026-91732?
CVE-2026-91732 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-91732?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91732, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-91732

Explore →

Is Your Infrastructure Affected by CVE-2026-91732?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.