CVE-2026-91731
HIGHCVSS 8.8/10EPSS 0.39%
Last modified
CVE-2026-91731 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. Type confusion in Compositing in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High). EPSS estimates a 0.39% chance of exploitation in the next 30 days.
Description
Type confusion in Compositing in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Chrome | >= 153.0.8010.47, < 153.0.8010.47 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-91731?
Type confusion in Compositing in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
How severe is CVE-2026-91731?
CVE-2026-91731 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.39% probability of exploitation in the next 30 days.
How do I fix CVE-2026-91731?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-91725Observable discrepancy in CSS in Google Chrome prior to 153.…5.3
- CVE-2026-91726Out of bounds read in WebGL in Google Chrome on on Android p…4.7
- CVE-2026-91727Incorrect reference resolution in Extensions in Google Chrom…8.1
- CVE-2026-91728Integer overflow in V8 in Google Chrome prior to 153.0.8010.…9.6
- CVE-2026-91729Use after free in DigitalCredentials in Google Chrome prior …9.6
- CVE-2026-91730Incomplete cleanup in GetUserMedia in Google Chrome prior to…3.1
- CVE-2026-91732Missing authorization in AppManifest in Google Chrome prior …
- CVE-2026-91733Improper state validation in Skia in Google Chrome prior to …8.3
- CVE-2026-91734Incorrect authorization in Core in Google Chrome on on Windo…7.4
- CVE-2026-91735Incorrect authorization in WebUI in Google Chrome prior to 1…8.3
- CVE-2026-91736Use after free in DOM in Google Chrome prior to 153.0.8010.4…8.8
- CVE-2026-91737Use after free in PDF in Google Chrome prior to 153.0.8010.4…8.8
Are you affected by CVE-2026-91731?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST