# Google Chrome Dev (EXE) 158.0.8106.0 Google Chrome Dev (EXE) 158.0.8106.0, released October 15, 2026, fixes 194 CVEs in Google Chrome Dev (EXE). None of them is reported as exploited. Patch Radar priority: Urgent. The latest Google Chrome Dev (EXE) is 159.0.8144.0, which also fixes every one of these CVEs. - Web page: https://patchblox.com/security/fix/windows-app/google.chrome.dev.exe-158.0.8106.0 - Platform: Windows apps - Released: Oct 15, 2026 - Priority: Urgent (Closes CVE-2026-121156, rated Critical) - CVEs: 194, exploited: 0, on CISA KEV: 0 - Superseded by: [Google Chrome Dev (EXE) 159.0.8144.0](https://patchblox.com/security/data/product/windows-app/google-chrome-dev-exe.md), the latest version, which also fixes every CVE listed here ## Applies to | Product | Release | Fixed in | |---|---|---| | [Google Chrome Dev (EXE)](https://patchblox.com/security/data/product/windows-app/google-chrome-dev-exe.md) | | 158.0.8106.0 | ## CVEs this fix closes | CVE | Priority | Title | CVSS | EPSS | Exploitation | |---|---|---|---:|---:|---| | [CVE-2026-121156](https://patchblox.com/security/data/cve/CVE-2026-121156.md) | Urgent | Google Chrome: Buffer overflow | 9.6 | 0.0048 | | | [CVE-2026-121035](https://patchblox.com/security/data/cve/CVE-2026-121035.md) | Urgent | Chromium CVE-2026-121035: Use after free | 9.6 | 0.0044 | | | [CVE-2026-121126](https://patchblox.com/security/data/cve/CVE-2026-121126.md) | Urgent | Chromium CVE-2026-121126: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121148](https://patchblox.com/security/data/cve/CVE-2026-121148.md) | Urgent | Google Chrome: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121060](https://patchblox.com/security/data/cve/CVE-2026-121060.md) | Urgent | Google Chrome: Incorrect authorization | 9.6 | 0.0041 | | | [CVE-2026-121071](https://patchblox.com/security/data/cve/CVE-2026-121071.md) | Urgent | Google Chrome: Incorrect authorization | 9.6 | 0.0040 | | | [CVE-2026-121203](https://patchblox.com/security/data/cve/CVE-2026-121203.md) | Urgent | Chromium CVE-2026-121203: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121076](https://patchblox.com/security/data/cve/CVE-2026-121076.md) | Urgent | Google Chrome: Use after free | 9.6 | 0.0034 | | | [CVE-2026-121077](https://patchblox.com/security/data/cve/CVE-2026-121077.md) | Urgent | Google Chrome: Use after free | 9.6 | 0.0034 | | | [CVE-2026-121073](https://patchblox.com/security/data/cve/CVE-2026-121073.md) | Urgent | Google Chrome: Use after free | 9.6 | 0.0026 | | | [CVE-2026-121127](https://patchblox.com/security/data/cve/CVE-2026-121127.md) | High | Chromium CVE-2026-121127: Use after free | 8.8 | 0.0047 | | | [CVE-2026-121129](https://patchblox.com/security/data/cve/CVE-2026-121129.md) | High | Chromium CVE-2026-121129: Use after free | 8.8 | 0.0047 | | | [CVE-2026-121037](https://patchblox.com/security/data/cve/CVE-2026-121037.md) | High | Chromium CVE-2026-121037: Out of bounds write | 9.6 | 0.0045 | | | [CVE-2026-121086](https://patchblox.com/security/data/cve/CVE-2026-121086.md) | High | Chromium CVE-2026-121086: Buffer overflow | 9.6 | 0.0045 | | | [CVE-2026-121249](https://patchblox.com/security/data/cve/CVE-2026-121249.md) | High | Chromium CVE-2026-121249: Buffer overflow | 9.6 | 0.0045 | | | [CVE-2026-121057](https://patchblox.com/security/data/cve/CVE-2026-121057.md) | High | Google Chrome: Type confusion | 8.8 | 0.0044 | | | [CVE-2026-121034](https://patchblox.com/security/data/cve/CVE-2026-121034.md) | High | Chromium CVE-2026-121034: Use after free | 9.6 | 0.0042 | | | [CVE-2026-121089](https://patchblox.com/security/data/cve/CVE-2026-121089.md) | High | Chromium CVE-2026-121089: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121114](https://patchblox.com/security/data/cve/CVE-2026-121114.md) | High | Chromium CVE-2026-121114: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121185](https://patchblox.com/security/data/cve/CVE-2026-121185.md) | High | Chromium CVE-2026-121185: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121189](https://patchblox.com/security/data/cve/CVE-2026-121189.md) | High | Chromium CVE-2026-121189: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121214](https://patchblox.com/security/data/cve/CVE-2026-121214.md) | High | Chromium CVE-2026-121214: Use after free | 9.6 | 0.0041 | | | [CVE-2026-121030](https://patchblox.com/security/data/cve/CVE-2026-121030.md) | High | Chromium CVE-2026-121030: Incorrect authorization | 9.6 | 0.0041 | | | [CVE-2026-121044](https://patchblox.com/security/data/cve/CVE-2026-121044.md) | High | Google Chrome: Use after free | 8.8 | 0.0041 | | | [CVE-2026-121052](https://patchblox.com/security/data/cve/CVE-2026-121052.md) | High | Google Chrome: Use after free | 8.8 | 0.0041 | | | [CVE-2026-121068](https://patchblox.com/security/data/cve/CVE-2026-121068.md) | High | Google Chrome: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121078](https://patchblox.com/security/data/cve/CVE-2026-121078.md) | High | Chromium CVE-2026-121078: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121082](https://patchblox.com/security/data/cve/CVE-2026-121082.md) | High | Chromium CVE-2026-121082: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121094](https://patchblox.com/security/data/cve/CVE-2026-121094.md) | High | Chromium CVE-2026-121094: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121137](https://patchblox.com/security/data/cve/CVE-2026-121137.md) | High | Chromium CVE-2026-121137: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121210](https://patchblox.com/security/data/cve/CVE-2026-121210.md) | High | Chromium CVE-2026-121210: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121218](https://patchblox.com/security/data/cve/CVE-2026-121218.md) | High | Chromium CVE-2026-121218: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121221](https://patchblox.com/security/data/cve/CVE-2026-121221.md) | High | Chromium CVE-2026-121221: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121226](https://patchblox.com/security/data/cve/CVE-2026-121226.md) | High | Chromium CVE-2026-121226: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121228](https://patchblox.com/security/data/cve/CVE-2026-121228.md) | High | Chromium CVE-2026-121228: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121233](https://patchblox.com/security/data/cve/CVE-2026-121233.md) | High | Chromium CVE-2026-121233: Type confusion | 8.8 | 0.0040 | | | [CVE-2026-121180](https://patchblox.com/security/data/cve/CVE-2026-121180.md) | High | Chromium CVE-2026-121180: Buffer overflow | 8.8 | 0.0040 | | | [CVE-2026-121098](https://patchblox.com/security/data/cve/CVE-2026-121098.md) | High | Chromium CVE-2026-121098: Improper state validation | 8.3 | 0.0040 | | | [CVE-2026-121131](https://patchblox.com/security/data/cve/CVE-2026-121131.md) | High | Chromium CVE-2026-121131: Use after free | 9.6 | 0.0038 | | | [CVE-2026-121036](https://patchblox.com/security/data/cve/CVE-2026-121036.md) | High | Chromium CVE-2026-121036: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121061](https://patchblox.com/security/data/cve/CVE-2026-121061.md) | High | Google Chrome: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121070](https://patchblox.com/security/data/cve/CVE-2026-121070.md) | High | Google Chrome: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121083](https://patchblox.com/security/data/cve/CVE-2026-121083.md) | High | Chromium CVE-2026-121083: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121097](https://patchblox.com/security/data/cve/CVE-2026-121097.md) | High | Chromium CVE-2026-121097: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121100](https://patchblox.com/security/data/cve/CVE-2026-121100.md) | High | Chromium CVE-2026-121100: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121117](https://patchblox.com/security/data/cve/CVE-2026-121117.md) | High | Chromium CVE-2026-121117: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121118](https://patchblox.com/security/data/cve/CVE-2026-121118.md) | High | Chromium CVE-2026-121118: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121119](https://patchblox.com/security/data/cve/CVE-2026-121119.md) | High | Chromium CVE-2026-121119: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121123](https://patchblox.com/security/data/cve/CVE-2026-121123.md) | High | Chromium CVE-2026-121123: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121128](https://patchblox.com/security/data/cve/CVE-2026-121128.md) | High | Chromium CVE-2026-121128: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121168](https://patchblox.com/security/data/cve/CVE-2026-121168.md) | High | Google Chrome: Improper resource exposure | 8.8 | 0.0037 | | | [CVE-2026-121181](https://patchblox.com/security/data/cve/CVE-2026-121181.md) | High | Chromium CVE-2026-121181: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121182](https://patchblox.com/security/data/cve/CVE-2026-121182.md) | High | Chromium CVE-2026-121182: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121188](https://patchblox.com/security/data/cve/CVE-2026-121188.md) | High | Chromium CVE-2026-121188: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121201](https://patchblox.com/security/data/cve/CVE-2026-121201.md) | High | Chromium CVE-2026-121201: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121208](https://patchblox.com/security/data/cve/CVE-2026-121208.md) | High | Chromium CVE-2026-121208: Out of bounds read | 8.8 | 0.0037 | | | [CVE-2026-121238](https://patchblox.com/security/data/cve/CVE-2026-121238.md) | High | Chromium CVE-2026-121238: Use after free | 8.8 | 0.0037 | | | [CVE-2026-121200](https://patchblox.com/security/data/cve/CVE-2026-121200.md) | High | Chromium CVE-2026-121200: Incorrect reference resolution | 9.6 | 0.0037 | | | [CVE-2026-121112](https://patchblox.com/security/data/cve/CVE-2026-121112.md) | High | Google Chrome: Out of bounds read | 8.3 | 0.0036 | | | [CVE-2026-121140](https://patchblox.com/security/data/cve/CVE-2026-121140.md) | High | Google Chrome: Out of bounds read | 8.3 | 0.0036 | | | [CVE-2026-121178](https://patchblox.com/security/data/cve/CVE-2026-121178.md) | High | Chromium CVE-2026-121178: Use after free | 8.3 | 0.0036 | | | [CVE-2026-121124](https://patchblox.com/security/data/cve/CVE-2026-121124.md) | High | Chromium CVE-2026-121124: Improper adherence to coding standards | 8.8 | 0.0036 | | | [CVE-2026-121184](https://patchblox.com/security/data/cve/CVE-2026-121184.md) | High | Chromium CVE-2026-121184: Out of bounds read | 8.8 | 0.0036 | | | [CVE-2026-121047](https://patchblox.com/security/data/cve/CVE-2026-121047.md) | High | Google Chrome: Buffer overflow | 8.8 | 0.0036 | | | [CVE-2026-121113](https://patchblox.com/security/data/cve/CVE-2026-121113.md) | High | Chromium CVE-2026-121113: Buffer overflow | 8.8 | 0.0035 | | | [CVE-2026-121179](https://patchblox.com/security/data/cve/CVE-2026-121179.md) | High | Chromium CVE-2026-121179: Use after free | 8.8 | 0.0035 | | | [CVE-2026-121183](https://patchblox.com/security/data/cve/CVE-2026-121183.md) | High | Chromium CVE-2026-121183: Incorrect authorization | 8.3 | 0.0035 | | | [CVE-2026-121202](https://patchblox.com/security/data/cve/CVE-2026-121202.md) | High | Chromium CVE-2026-121202: Use after free | 9.6 | 0.0033 | | | [CVE-2026-121104](https://patchblox.com/security/data/cve/CVE-2026-121104.md) | High | Chromium CVE-2026-121104: Incorrect authorization | 9.6 | 0.0033 | | | [CVE-2026-121166](https://patchblox.com/security/data/cve/CVE-2026-121166.md) | High | Google Chrome: Type confusion | 8.8 | 0.0032 | | | [CVE-2026-121174](https://patchblox.com/security/data/cve/CVE-2026-121174.md) | High | Chromium CVE-2026-121174: Missing authorization | 8.8 | 0.0032 | | | [CVE-2026-121069](https://patchblox.com/security/data/cve/CVE-2026-121069.md) | High | Google Chrome: Use after free | 8.8 | 0.0032 | | | [CVE-2026-121092](https://patchblox.com/security/data/cve/CVE-2026-121092.md) | High | Chromium CVE-2026-121092: Uncontrolled recursion | 8.8 | 0.0032 | | | [CVE-2026-121134](https://patchblox.com/security/data/cve/CVE-2026-121134.md) | High | Chromium CVE-2026-121134: Information loss | 8.8 | 0.0031 | | | [CVE-2026-121204](https://patchblox.com/security/data/cve/CVE-2026-121204.md) | High | Chromium CVE-2026-121204: Incomplete cleanup | 8.8 | 0.0031 | | | [CVE-2026-121250](https://patchblox.com/security/data/cve/CVE-2026-121250.md) | High | Chromium CVE-2026-121250: Use after free | 9.6 | 0.0031 | | | [CVE-2026-121257](https://patchblox.com/security/data/cve/CVE-2026-121257.md) | High | Chromium CVE-2026-121257: Use after free | 9.6 | 0.0031 | | | [CVE-2026-121256](https://patchblox.com/security/data/cve/CVE-2026-121256.md) | High | Chromium CVE-2026-121256: Use of released resource | 8.3 | 0.0030 | | | [CVE-2026-121084](https://patchblox.com/security/data/cve/CVE-2026-121084.md) | High | Chromium CVE-2026-121084: Out of bounds read | 8.3 | 0.0030 | | | [CVE-2026-121219](https://patchblox.com/security/data/cve/CVE-2026-121219.md) | High | Chromium CVE-2026-121219: Integer overflow | 8.3 | 0.0030 | | | [CVE-2026-121048](https://patchblox.com/security/data/cve/CVE-2026-121048.md) | High | Google Chrome: Race condition | 8.8 | 0.0030 | | | [CVE-2026-121079](https://patchblox.com/security/data/cve/CVE-2026-121079.md) | High | Chromium CVE-2026-121079: Race condition | 8.8 | 0.0030 | | | [CVE-2026-121170](https://patchblox.com/security/data/cve/CVE-2026-121170.md) | High | Google Chrome: Improper resource control | 8.8 | 0.0029 | | | [CVE-2026-121163](https://patchblox.com/security/data/cve/CVE-2026-121163.md) | High | Google Chrome: Improper input validation | 8.3 | 0.0029 | | | [CVE-2026-121211](https://patchblox.com/security/data/cve/CVE-2026-121211.md) | High | Chromium CVE-2026-121211: Use after free | 8.3 | 0.0027 | | | [CVE-2026-121171](https://patchblox.com/security/data/cve/CVE-2026-121171.md) | High | Google Chrome: Confused deputy | 8.8 | 0.0026 | | | [CVE-2026-121212](https://patchblox.com/security/data/cve/CVE-2026-121212.md) | High | Chromium CVE-2026-121212: Incorrect authorization | 8.8 | 0.0026 | | | [CVE-2026-121065](https://patchblox.com/security/data/cve/CVE-2026-121065.md) | High | Google Chrome: Incorrect authorization | 8.8 | 0.0026 | | | [CVE-2026-121102](https://patchblox.com/security/data/cve/CVE-2026-121102.md) | High | Chromium CVE-2026-121102: Missing authorization | 8.8 | 0.0026 | | | [CVE-2026-121107](https://patchblox.com/security/data/cve/CVE-2026-121107.md) | High | Chromium CVE-2026-121107: Incorrect authorization | 8.8 | 0.0026 | | | [CVE-2026-121108](https://patchblox.com/security/data/cve/CVE-2026-121108.md) | High | Chromium CVE-2026-121108: Confused deputy | 8.8 | 0.0026 | | | [CVE-2026-121205](https://patchblox.com/security/data/cve/CVE-2026-121205.md) | High | Chromium CVE-2026-121205: Incorrect authorization | 8.8 | 0.0026 | | | [CVE-2026-121222](https://patchblox.com/security/data/cve/CVE-2026-121222.md) | High | Chromium CVE-2026-121222: Incorrect authorization | 8.8 | 0.0026 | | | [CVE-2026-121251](https://patchblox.com/security/data/cve/CVE-2026-121251.md) | High | Chromium CVE-2026-121251: Missing authorization | 8.8 | 0.0026 | | | [CVE-2026-121252](https://patchblox.com/security/data/cve/CVE-2026-121252.md) | High | Chromium CVE-2026-121252: Incorrect authorization | 8.8 | 0.0026 | | | [CVE-2026-121087](https://patchblox.com/security/data/cve/CVE-2026-121087.md) | High | Chromium CVE-2026-121087: Improper input validation | 8.8 | 0.0026 | | | [CVE-2026-121120](https://patchblox.com/security/data/cve/CVE-2026-121120.md) | High | Chromium CVE-2026-121120: Improper input validation | 8.8 | 0.0026 | | | [CVE-2026-121135](https://patchblox.com/security/data/cve/CVE-2026-121135.md) | High | Chromium CVE-2026-121135: Security issue | 8.8 | 0.0026 | | | [CVE-2026-121236](https://patchblox.com/security/data/cve/CVE-2026-121236.md) | High | Chromium CVE-2026-121236: Improper input validation | 8.8 | 0.0026 | | | [CVE-2026-121195](https://patchblox.com/security/data/cve/CVE-2026-121195.md) | High | Chromium CVE-2026-121195: Incorrect authorization | 8.8 | 0.0022 | | | [CVE-2026-121198](https://patchblox.com/security/data/cve/CVE-2026-121198.md) | High | Chromium CVE-2026-121198: Confused deputy | 8.8 | 0.0022 | | | [CVE-2026-121054](https://patchblox.com/security/data/cve/CVE-2026-121054.md) | High | Google Chrome: Improper state validation | 8.8 | 0.0021 | | | [CVE-2026-121230](https://patchblox.com/security/data/cve/CVE-2026-121230.md) | High | Chromium CVE-2026-121230: Race condition | 8.3 | 0.0020 | | | [CVE-2026-121217](https://patchblox.com/security/data/cve/CVE-2026-121217.md) | High | Chromium CVE-2026-121217: Use after free | 7.5 | 0.0013 | | | [CVE-2026-121064](https://patchblox.com/security/data/cve/CVE-2026-121064.md) | High | Google Chrome: Improper input validation | 7.8 | 0.0009 | | | [CVE-2026-121072](https://patchblox.com/security/data/cve/CVE-2026-121072.md) | Routine | Google Chrome: Uninitialized resource | 6.5 | 0.0033 | | | [CVE-2026-121099](https://patchblox.com/security/data/cve/CVE-2026-121099.md) | Routine | Chromium CVE-2026-121099: Information leak | 6.5 | 0.0030 | | | [CVE-2026-121105](https://patchblox.com/security/data/cve/CVE-2026-121105.md) | Routine | Chromium CVE-2026-121105: Information leak | 6.5 | 0.0030 | | | [CVE-2026-121161](https://patchblox.com/security/data/cve/CVE-2026-121161.md) | Routine | Google Chrome: Information leak | 6.5 | 0.0030 | | | [CVE-2026-121059](https://patchblox.com/security/data/cve/CVE-2026-121059.md) | Routine | Google Chrome: Information leak | 6.5 | 0.0030 | | | [CVE-2026-121187](https://patchblox.com/security/data/cve/CVE-2026-121187.md) | Routine | Chromium CVE-2026-121187: Observable discrepancy | 5.3 | 0.0029 | | | [CVE-2026-121033](https://patchblox.com/security/data/cve/CVE-2026-121033.md) | Routine | Google Chrome: Uninitialized resource | 0.0 | 0.0029 | | | [CVE-2026-121038](https://patchblox.com/security/data/cve/CVE-2026-121038.md) | Routine | Chromium CVE-2026-121038: Information leak | 6.5 | 0.0028 | | | [CVE-2026-121063](https://patchblox.com/security/data/cve/CVE-2026-121063.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0027 | | | [CVE-2026-121213](https://patchblox.com/security/data/cve/CVE-2026-121213.md) | Routine | Chromium CVE-2026-121213: Uninitialized resource | 6.5 | 0.0027 | | | [CVE-2026-121095](https://patchblox.com/security/data/cve/CVE-2026-121095.md) | Routine | Chromium CVE-2026-121095: Uninitialized resource | 0.0 | 0.0027 | | | [CVE-2026-121173](https://patchblox.com/security/data/cve/CVE-2026-121173.md) | Routine | Google Chrome: Uninitialized resource | 0.0 | 0.0027 | | | [CVE-2026-121125](https://patchblox.com/security/data/cve/CVE-2026-121125.md) | Routine | Chromium CVE-2026-121125: Information leak | 5.3 | 0.0027 | | | [CVE-2026-121130](https://patchblox.com/security/data/cve/CVE-2026-121130.md) | Routine | Chromium CVE-2026-121130: Observable discrepancy | 5.3 | 0.0027 | | | [CVE-2026-121080](https://patchblox.com/security/data/cve/CVE-2026-121080.md) | Routine | Chromium CVE-2026-121080: Use after free | 4.3 | 0.0027 | | | [CVE-2026-121031](https://patchblox.com/security/data/cve/CVE-2026-121031.md) | Routine | Chromium CVE-2026-121031: Missing authorization | 0.0 | 0.0027 | | | [CVE-2026-121032](https://patchblox.com/security/data/cve/CVE-2026-121032.md) | Routine | Chromium CVE-2026-121032: Out of bounds read | 0.0 | 0.0027 | | | [CVE-2026-121121](https://patchblox.com/security/data/cve/CVE-2026-121121.md) | Routine | Chromium CVE-2026-121121: UI misrepresentation | 5.4 | 0.0026 | | | [CVE-2026-121122](https://patchblox.com/security/data/cve/CVE-2026-121122.md) | Routine | Chromium CVE-2026-121122: UI misrepresentation | 5.4 | 0.0026 | | | [CVE-2026-121091](https://patchblox.com/security/data/cve/CVE-2026-121091.md) | Routine | Chromium CVE-2026-121091: Incorrect authorization | 5.3 | 0.0026 | | | [CVE-2026-121138](https://patchblox.com/security/data/cve/CVE-2026-121138.md) | Routine | Chromium CVE-2026-121138: Observable discrepancy | 6.5 | 0.0025 | | | [CVE-2026-121235](https://patchblox.com/security/data/cve/CVE-2026-121235.md) | Routine | Chromium CVE-2026-121235: Information leak | 6.5 | 0.0025 | | | [CVE-2026-121243](https://patchblox.com/security/data/cve/CVE-2026-121243.md) | Routine | Chromium CVE-2026-121243: Information leak | 6.5 | 0.0025 | | | [CVE-2026-121160](https://patchblox.com/security/data/cve/CVE-2026-121160.md) | Routine | Google Chrome: Out of bounds read | 0.0 | 0.0025 | | | [CVE-2026-121176](https://patchblox.com/security/data/cve/CVE-2026-121176.md) | Routine | Chromium CVE-2026-121176: Uninitialized resource | 6.5 | 0.0025 | | | [CVE-2026-121239](https://patchblox.com/security/data/cve/CVE-2026-121239.md) | Routine | Chromium CVE-2026-121239: Information leak | 6.5 | 0.0025 | | | [CVE-2026-121254](https://patchblox.com/security/data/cve/CVE-2026-121254.md) | Routine | Chromium CVE-2026-121254: Information leak | 6.5 | 0.0025 | | | [CVE-2026-121143](https://patchblox.com/security/data/cve/CVE-2026-121143.md) | Routine | Google Chrome: Uninitialized resource | 0.0 | 0.0024 | | | [CVE-2026-121207](https://patchblox.com/security/data/cve/CVE-2026-121207.md) | Routine | Chromium CVE-2026-121207: Uninitialized resource | 0.0 | 0.0024 | | | [CVE-2026-121227](https://patchblox.com/security/data/cve/CVE-2026-121227.md) | Routine | Chromium CVE-2026-121227: Uninitialized resource | 0.0 | 0.0024 | | | [CVE-2026-121088](https://patchblox.com/security/data/cve/CVE-2026-121088.md) | Routine | Chromium CVE-2026-121088: Missing authorization | 6.5 | 0.0024 | | | [CVE-2026-121255](https://patchblox.com/security/data/cve/CVE-2026-121255.md) | Routine | Chromium CVE-2026-121255: Incorrect authorization | 6.5 | 0.0024 | | | [CVE-2026-121081](https://patchblox.com/security/data/cve/CVE-2026-121081.md) | Routine | Chromium CVE-2026-121081: UI misrepresentation | 5.9 | 0.0023 | | | [CVE-2026-121237](https://patchblox.com/security/data/cve/CVE-2026-121237.md) | Routine | Chromium CVE-2026-121237: Improper state validation | 0.0 | 0.0023 | | | [CVE-2026-121196](https://patchblox.com/security/data/cve/CVE-2026-121196.md) | Routine | Google Chrome: Privilege elevation | 0.0 | 0.0023 | | | [CVE-2026-121132](https://patchblox.com/security/data/cve/CVE-2026-121132.md) | Routine | Chromium CVE-2026-121132: Information leak | 6.5 | 0.0023 | | | [CVE-2026-121158](https://patchblox.com/security/data/cve/CVE-2026-121158.md) | Routine | Google Chrome: Information leak | 6.5 | 0.0023 | | | [CVE-2026-121042](https://patchblox.com/security/data/cve/CVE-2026-121042.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0022 | | | [CVE-2026-121062](https://patchblox.com/security/data/cve/CVE-2026-121062.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0022 | | | [CVE-2026-121164](https://patchblox.com/security/data/cve/CVE-2026-121164.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0022 | | | [CVE-2026-121167](https://patchblox.com/security/data/cve/CVE-2026-121167.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0022 | | | [CVE-2026-121194](https://patchblox.com/security/data/cve/CVE-2026-121194.md) | Routine | Chromium CVE-2026-121194: Missing authorization | 5.3 | 0.0022 | | | [CVE-2026-121197](https://patchblox.com/security/data/cve/CVE-2026-121197.md) | Routine | Chromium CVE-2026-121197: Out of bounds read | 0.0 | 0.0022 | | | [CVE-2026-121223](https://patchblox.com/security/data/cve/CVE-2026-121223.md) | Routine | Chromium CVE-2026-121223: Observable discrepancy | 0.0 | 0.0022 | | | [CVE-2026-121055](https://patchblox.com/security/data/cve/CVE-2026-121055.md) | Routine | Google Chrome: Incomplete cleanup | 0.0 | 0.0022 | | | [CVE-2026-121157](https://patchblox.com/security/data/cve/CVE-2026-121157.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0021 | | | [CVE-2026-121242](https://patchblox.com/security/data/cve/CVE-2026-121242.md) | Routine | Chromium CVE-2026-121242: Improper input validation | 0.0 | 0.0021 | | | [CVE-2026-121046](https://patchblox.com/security/data/cve/CVE-2026-121046.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0021 | | | [CVE-2026-121085](https://patchblox.com/security/data/cve/CVE-2026-121085.md) | Routine | Chromium CVE-2026-121085: Incorrect authorization | 0.0 | 0.0021 | | | [CVE-2026-121101](https://patchblox.com/security/data/cve/CVE-2026-121101.md) | Routine | Chromium CVE-2026-121101: Missing authorization | 0.0 | 0.0021 | | | [CVE-2026-121253](https://patchblox.com/security/data/cve/CVE-2026-121253.md) | Routine | Chromium CVE-2026-121253: Missing authorization | 0.0 | 0.0021 | | | [CVE-2026-121029](https://patchblox.com/security/data/cve/CVE-2026-121029.md) | Routine | Chromium CVE-2026-121029: Incorrect authorization | 0.0 | 0.0020 | | | [CVE-2026-121043](https://patchblox.com/security/data/cve/CVE-2026-121043.md) | Routine | Google Chrome: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-121067](https://patchblox.com/security/data/cve/CVE-2026-121067.md) | Routine | Google Chrome: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-121206](https://patchblox.com/security/data/cve/CVE-2026-121206.md) | Routine | Chromium CVE-2026-121206: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-121216](https://patchblox.com/security/data/cve/CVE-2026-121216.md) | Routine | Chromium CVE-2026-121216: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-121244](https://patchblox.com/security/data/cve/CVE-2026-121244.md) | Routine | Chromium CVE-2026-121244: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-121111](https://patchblox.com/security/data/cve/CVE-2026-121111.md) | Routine | Chromium CVE-2026-121111: Incorrect authorization | 0.0 | 0.0020 | | | [CVE-2026-121159](https://patchblox.com/security/data/cve/CVE-2026-121159.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0020 | | | [CVE-2026-121093](https://patchblox.com/security/data/cve/CVE-2026-121093.md) | Routine | Chromium CVE-2026-121093: Out of bounds read | 0.0 | 0.0020 | | | [CVE-2026-121215](https://patchblox.com/security/data/cve/CVE-2026-121215.md) | Routine | Chromium CVE-2026-121215: UI misrepresentation | 5.4 | 0.0019 | | | [CVE-2026-121172](https://patchblox.com/security/data/cve/CVE-2026-121172.md) | Routine | Google Chrome: Incorrect authorization | 5.4 | 0.0019 | | | [CVE-2026-121040](https://patchblox.com/security/data/cve/CVE-2026-121040.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0019 | | | [CVE-2026-121075](https://patchblox.com/security/data/cve/CVE-2026-121075.md) | Routine | Google Chrome: Missing authorization | 0.0 | 0.0019 | | | [CVE-2026-121220](https://patchblox.com/security/data/cve/CVE-2026-121220.md) | Routine | Chromium CVE-2026-121220: Incorrect authorization | 0.0 | 0.0019 | | | [CVE-2026-121225](https://patchblox.com/security/data/cve/CVE-2026-121225.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0019 | | | [CVE-2026-121231](https://patchblox.com/security/data/cve/CVE-2026-121231.md) | Routine | Chromium CVE-2026-121231: Incorrect authorization | 0.0 | 0.0019 | | | [CVE-2026-121051](https://patchblox.com/security/data/cve/CVE-2026-121051.md) | Routine | Google Chrome: UI misrepresentation | 0.0 | 0.0019 | | | [CVE-2026-121142](https://patchblox.com/security/data/cve/CVE-2026-121142.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0019 | | | [CVE-2026-121169](https://patchblox.com/security/data/cve/CVE-2026-121169.md) | Routine | Google Chrome: Missing authorization | 0.0 | 0.0019 | | | [CVE-2026-121209](https://patchblox.com/security/data/cve/CVE-2026-121209.md) | Routine | Chromium CVE-2026-121209: UI misrepresentation | 0.0 | 0.0019 | | | [CVE-2026-121041](https://patchblox.com/security/data/cve/CVE-2026-121041.md) | Routine | Google Chrome: Missing authorization | 6.5 | 0.0018 | | | [CVE-2026-121115](https://patchblox.com/security/data/cve/CVE-2026-121115.md) | Routine | Chromium CVE-2026-121115: Improper input validation | 0.0 | 0.0018 | | | [CVE-2026-121245](https://patchblox.com/security/data/cve/CVE-2026-121245.md) | Routine | Chromium CVE-2026-121245: Race condition | 5.3 | 0.0018 | | | [CVE-2026-121066](https://patchblox.com/security/data/cve/CVE-2026-121066.md) | Routine | Google Chrome: Incorrect authorization | 0.0 | 0.0018 | | | [CVE-2026-121136](https://patchblox.com/security/data/cve/CVE-2026-121136.md) | Routine | Chromium CVE-2026-121136: Missing authorization | 0.0 | 0.0018 | | | [CVE-2026-121193](https://patchblox.com/security/data/cve/CVE-2026-121193.md) | Routine | Chromium CVE-2026-121193: Incorrect authorization | 0.0 | 0.0018 | | | [CVE-2026-121248](https://patchblox.com/security/data/cve/CVE-2026-121248.md) | Routine | Chromium CVE-2026-121248: Incorrect authorization | 0.0 | 0.0018 | | | [CVE-2026-121175](https://patchblox.com/security/data/cve/CVE-2026-121175.md) | Routine | Chromium CVE-2026-121175: Improper resource exposure | 0.0 | 0.0017 | | | [CVE-2026-121162](https://patchblox.com/security/data/cve/CVE-2026-121162.md) | Routine | Google Chrome: UI misrepresentation | 5.4 | 0.0017 | | | [CVE-2026-121103](https://patchblox.com/security/data/cve/CVE-2026-121103.md) | Routine | Chromium CVE-2026-121103: Incorrect authorization | 0.0 | 0.0016 | | | [CVE-2026-121240](https://patchblox.com/security/data/cve/CVE-2026-121240.md) | Routine | Chromium CVE-2026-121240: Improper input validation | 0.0 | 0.0016 | | | [CVE-2026-121190](https://patchblox.com/security/data/cve/CVE-2026-121190.md) | Routine | Chromium CVE-2026-121190: UI misrepresentation | 0.0 | 0.0016 | | | [CVE-2026-121141](https://patchblox.com/security/data/cve/CVE-2026-121141.md) | Routine | Google Chrome: Improper input validation | 5.4 | 0.0015 | | | [CVE-2026-121039](https://patchblox.com/security/data/cve/CVE-2026-121039.md) | Routine | Chromium CVE-2026-121039: Incorrect authorization | 5.3 | 0.0012 | | | [CVE-2026-121109](https://patchblox.com/security/data/cve/CVE-2026-121109.md) | Routine | Chromium CVE-2026-121109: Inadequate encryption strength | 0.0 | 0.0011 | | | [CVE-2026-121096](https://patchblox.com/security/data/cve/CVE-2026-121096.md) | Routine | Chromium CVE-2026-121096: Incomplete cleanup | 0.0 | 0.0010 | | | [CVE-2026-121049](https://patchblox.com/security/data/cve/CVE-2026-121049.md) | Routine | Google Chrome: Out of bounds read | 3.3 | 0.0010 | | | [CVE-2026-121232](https://patchblox.com/security/data/cve/CVE-2026-121232.md) | Routine | Chromium CVE-2026-121232: Incorrect authorization | 5.1 | 0.0008 | | --- Data as of 2026-11-11T07:45:43Z 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.