major vulnerability· requires attention

Remote RCE in Google Chrome, a widely deployed browser; exploitable code execution outside sandbox risks mass host compromise and broad newsworthy impact.

Web

CVE-2026-91716

9.6

Critical

EPSS 0.31%Patch available

Use-after-free in Chrome <153.0.8010.47 enables remote code execution 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.31%top 77% of scored CVEs

Published 15 Sept 2026Analysed here 17 Sept 2026CVSS scored by CISA

common questions

Is CVE-2026-91716 being exploited?

Not confirmed. CVE-2026-91716 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.31% probability of exploitation in the next 30 days.

How severe is CVE-2026-91716?

CVE-2026-91716 is rated Critical with a CVSS score of 9.6. 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-91716?

Yes. A fix has been recorded for CVE-2026-91716. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-91716 affect?

CVE-2026-91716 affects Google Chrome (Desktop) versions 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-91716?

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 (Desktop) versions prior to 153.0.8010.47

impact

Remote code execution outside Chrome sandbox via crafted HTML, enabling arbitrary code execution and potential host compromise.

action required

Immediate action required

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: total

Assessed by CISA 16 Sept 2026 (SSVC 2.0.3).

timeline

15 Sept 2026Published
16 Sept 2026CISA SSVC assessment: exploitation none · same day later
17 Sept 2026CVE record last updated · 1 day later
17 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

NVD CVE.org CVE Details Source

2 references in the CVE record: 2 links

Linkchromereleases.googleblog.com /2026/09/stable-channel-update-for-desktop_0541751186.html
Linkissues.chromium.org /issues/554558368

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