# Google Chrome 153.0.8010.48 Google Chrome 153.0.8010.48, released September 14, 2026, fixes 38 CVEs in Google Chrome. None of them is reported as exploited. Patch Radar priority: Urgent. The latest Google Chrome is 157.0.8103.51, which also fixes every one of these CVEs. - Web page: https://patchblox.com/security/fix/macos/com.google.chrome-153.0.8010.48 - Platform: macOS - Released: Sep 14, 2026 - Priority: Urgent (Closes CVE-2026-91721, rated Critical) - CVEs: 38, exploited: 0, on CISA KEV: 0 - Superseded by: [Google Chrome 157.0.8103.51](https://patchblox.com/security/data/product/macos/google-chrome.md), the latest version, which also fixes every CVE listed here ## Applies to | Product | Release | Fixed in | |---|---|---| | [Google Chrome](https://patchblox.com/security/data/product/macos/google-chrome.md) | | 153.0.8010.48 | ## CVEs this fix closes | CVE | Priority | Title | CVSS | EPSS | Exploitation | |---|---|---|---:|---:|---| | [CVE-2026-91721](https://patchblox.com/security/data/cve/CVE-2026-91721.md) | Urgent | Chromium CVE-2026-91721: Use after free | 8.8 | 0.0039 | | | [CVE-2026-91749](https://patchblox.com/security/data/cve/CVE-2026-91749.md) | Urgent | Chromium CVE-2026-91749: Use after free | 9.6 | 0.0038 | | | [CVE-2026-91731](https://patchblox.com/security/data/cve/CVE-2026-91731.md) | High | Chromium CVE-2026-91731: Type confusion | 8.8 | 0.0044 | | | [CVE-2026-91741](https://patchblox.com/security/data/cve/CVE-2026-91741.md) | High | Chromium CVE-2026-91741: Type confusion | 8.8 | 0.0044 | | | [CVE-2026-91728](https://patchblox.com/security/data/cve/CVE-2026-91728.md) | High | Chromium CVE-2026-91728: Integer overflow | 9.6 | 0.0041 | | | [CVE-2026-91709](https://patchblox.com/security/data/cve/CVE-2026-91709.md) | High | Chromium CVE-2026-91709: Type confusion | 8.8 | 0.0041 | | | [CVE-2026-91745](https://patchblox.com/security/data/cve/CVE-2026-91745.md) | High | Chromium CVE-2026-91745: Use after free | 8.8 | 0.0036 | | | [CVE-2026-91729](https://patchblox.com/security/data/cve/CVE-2026-91729.md) | High | Chromium CVE-2026-91729: Use after free | 9.6 | 0.0034 | | | [CVE-2026-91736](https://patchblox.com/security/data/cve/CVE-2026-91736.md) | High | Chromium CVE-2026-91736: Use after free | 8.8 | 0.0034 | | | [CVE-2026-91737](https://patchblox.com/security/data/cve/CVE-2026-91737.md) | High | Chromium CVE-2026-91737: Use after free | 8.8 | 0.0034 | | | [CVE-2026-91724](https://patchblox.com/security/data/cve/CVE-2026-91724.md) | High | Chromium CVE-2026-91724: Use after free | 8.3 | 0.0034 | | | [CVE-2026-91718](https://patchblox.com/security/data/cve/CVE-2026-91718.md) | High | Chromium CVE-2026-91718: Use after free | 9.6 | 0.0033 | | | [CVE-2026-91738](https://patchblox.com/security/data/cve/CVE-2026-91738.md) | High | Chromium CVE-2026-91738: Improper input validation | 9.6 | 0.0033 | | | [CVE-2026-91715](https://patchblox.com/security/data/cve/CVE-2026-91715.md) | High | Chromium CVE-2026-91715: Type confusion | 8.8 | 0.0033 | | | [CVE-2026-91733](https://patchblox.com/security/data/cve/CVE-2026-91733.md) | High | Chromium CVE-2026-91733: Improper state validation | 9.6 | 0.0032 | | | [CVE-2026-91710](https://patchblox.com/security/data/cve/CVE-2026-91710.md) | High | Chromium CVE-2026-91710: Use after free | 9.6 | 0.0031 | | | [CVE-2026-91716](https://patchblox.com/security/data/cve/CVE-2026-91716.md) | High | Chromium CVE-2026-91716: Use after free | 9.6 | 0.0031 | | | [CVE-2026-91711](https://patchblox.com/security/data/cve/CVE-2026-91711.md) | High | Chromium CVE-2026-91711: Out of bounds write | 8.8 | 0.0031 | | | [CVE-2026-91722](https://patchblox.com/security/data/cve/CVE-2026-91722.md) | High | Chromium CVE-2026-91722: Use after free | 8.8 | 0.0031 | | | [CVE-2026-91735](https://patchblox.com/security/data/cve/CVE-2026-91735.md) | High | Chromium CVE-2026-91735: Incorrect authorization | 8.3 | 0.0031 | | | [CVE-2026-91712](https://patchblox.com/security/data/cve/CVE-2026-91712.md) | High | Chromium CVE-2026-91712: Race condition | 8.3 | 0.0027 | | | [CVE-2026-91720](https://patchblox.com/security/data/cve/CVE-2026-91720.md) | High | Chromium CVE-2026-91720: Uninitialized resource | 9.6 | 0.0027 | | | [CVE-2026-91732](https://patchblox.com/security/data/cve/CVE-2026-91732.md) | High | Chromium CVE-2026-91732: Missing authorization | 8.1 | 0.0026 | | | [CVE-2026-91743](https://patchblox.com/security/data/cve/CVE-2026-91743.md) | High | Chromium CVE-2026-91743: Race condition | 8.3 | 0.0025 | | | [CVE-2026-91740](https://patchblox.com/security/data/cve/CVE-2026-91740.md) | High | Chromium CVE-2026-91740: Uninitialized resource | 9.6 | 0.0025 | | | [CVE-2026-91747](https://patchblox.com/security/data/cve/CVE-2026-91747.md) | High | Chromium CVE-2026-91747: Use after free | 9.6 | 0.0025 | | | [CVE-2026-91719](https://patchblox.com/security/data/cve/CVE-2026-91719.md) | High | Chromium CVE-2026-91719: Code injection | 8.1 | 0.0023 | | | [CVE-2026-91748](https://patchblox.com/security/data/cve/CVE-2026-91748.md) | High | Chromium CVE-2026-91748: Race condition | 8.3 | 0.0023 | | | [CVE-2026-91727](https://patchblox.com/security/data/cve/CVE-2026-91727.md) | High | Chromium CVE-2026-91727: Incorrect reference resolution | 8.1 | 0.0011 | | | [CVE-2026-91714](https://patchblox.com/security/data/cve/CVE-2026-91714.md) | Routine | Chromium CVE-2026-91714: Observable discrepancy | 5.3 | 0.0024 | | | [CVE-2026-91725](https://patchblox.com/security/data/cve/CVE-2026-91725.md) | Routine | Chromium CVE-2026-91725: Observable discrepancy | 5.3 | 0.0024 | | | [CVE-2026-91744](https://patchblox.com/security/data/cve/CVE-2026-91744.md) | Routine | Chromium CVE-2026-91744: Race condition | 5.3 | 0.0023 | | | [CVE-2026-91746](https://patchblox.com/security/data/cve/CVE-2026-91746.md) | Routine | Chromium CVE-2026-91746: Integer overflow | 4.3 | 0.0023 | | | [CVE-2026-91730](https://patchblox.com/security/data/cve/CVE-2026-91730.md) | Routine | Chromium CVE-2026-91730: Incomplete cleanup | 3.1 | 0.0023 | | | [CVE-2026-91739](https://patchblox.com/security/data/cve/CVE-2026-91739.md) | Routine | Chromium CVE-2026-91739: Missing authorization | 4.2 | 0.0019 | | | [CVE-2026-91713](https://patchblox.com/security/data/cve/CVE-2026-91713.md) | Routine | Chromium CVE-2026-91713: Missing authorization | 4.2 | 0.0019 | | | [CVE-2026-91723](https://patchblox.com/security/data/cve/CVE-2026-91723.md) | Routine | Chromium CVE-2026-91723: Race condition | 4.2 | 0.0017 | | | [CVE-2026-91708](https://patchblox.com/security/data/cve/CVE-2026-91708.md) | Routine | Chromium CVE-2026-91708: Race condition | 3.1 | 0.0016 | | --- Data as of 2026-11-11T01:43:54Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.