# OPENSUSE-SU-2026:22124-1: chromium security update OPENSUSE-SU-2026:22124-1, released November 7, 2026, fixes 293 CVEs in chromium (version 155.0.8059.84-bp160.1.1). None of them is reported as exploited. Patch Radar priority: Urgent. - Web page: https://patchblox.com/security/fix/linux/opensuse-su-2026-22124-1 - Platform: Linux - Released: Nov 7, 2026 - Priority: Urgent (Closes CVE-2026-106358, rated Critical) - CVEs: 293, exploited: 0, on CISA KEV: 0 - Vendor advisory: https://osv.dev/vulnerability/openSUSE-SU-2026:22124-1 ## Applies to | Product | Release | Fixed in | |---|---|---| | [chromium](https://patchblox.com/security/data/product/linux/chromium.md) | opensuse-leap 16.0 | 155.0.8059.84-bp160.1.1 | ## CVEs this fix closes | CVE | Priority | Title | CVSS | EPSS | Exploitation | |---|---|---|---:|---:|---| | [CVE-2026-106358](https://patchblox.com/security/data/cve/CVE-2026-106358.md) | Urgent | Chromium CVE-2026-106358: Use after free | 9.6 | 0.0057 | | | [CVE-2026-106197](https://patchblox.com/security/data/cve/CVE-2026-106197.md) | Urgent | Chromium CVE-2026-106197: Use after free | 9.6 | 0.0057 | | | [CVE-2026-110152](https://patchblox.com/security/data/cve/CVE-2026-110152.md) | Urgent | Chromium CVE-2026-110152: Buffer overflow | 9.6 | 0.0052 | | | [CVE-2026-110136](https://patchblox.com/security/data/cve/CVE-2026-110136.md) | Urgent | Chromium CVE-2026-110136: Use after free | 9.6 | 0.0043 | | | [CVE-2026-110161](https://patchblox.com/security/data/cve/CVE-2026-110161.md) | Urgent | Chromium CVE-2026-110161: Use after free | 9.6 | 0.0041 | | | [CVE-2026-110149](https://patchblox.com/security/data/cve/CVE-2026-110149.md) | Urgent | Chromium CVE-2026-110149: Use after free | 9.6 | 0.0041 | | | [CVE-2026-106382](https://patchblox.com/security/data/cve/CVE-2026-106382.md) | Urgent | Chromium CVE-2026-106382: Use after free | 9.6 | 0.0040 | | | [CVE-2026-110165](https://patchblox.com/security/data/cve/CVE-2026-110165.md) | Urgent | Chromium CVE-2026-110165: Use after free | 9.6 | 0.0039 | | | [CVE-2026-110922](https://patchblox.com/security/data/cve/CVE-2026-110922.md) | Urgent | Chromium CVE-2026-110922: Use after free in Prerender | 8.8 | 0.0038 | | | [CVE-2026-110148](https://patchblox.com/security/data/cve/CVE-2026-110148.md) | Urgent | Chromium CVE-2026-110148: Use after free | 8.8 | 0.0036 | | | [CVE-2026-110151](https://patchblox.com/security/data/cve/CVE-2026-110151.md) | Urgent | Chromium CVE-2026-110151: Use after free | 8.8 | 0.0036 | | | [CVE-2026-106347](https://patchblox.com/security/data/cve/CVE-2026-106347.md) | Urgent | Chromium CVE-2026-106347: Use after free | 8.8 | 0.0036 | | | [CVE-2026-106372](https://patchblox.com/security/data/cve/CVE-2026-106372.md) | Urgent | Chromium CVE-2026-106372: Incorrect authorization in UI | 9.6 | 0.0035 | | | [CVE-2026-106298](https://patchblox.com/security/data/cve/CVE-2026-106298.md) | Urgent | Chromium CVE-2026-106298: Use after free in Chrome Tabs | 9.6 | 0.0035 | | | [CVE-2026-106414](https://patchblox.com/security/data/cve/CVE-2026-106414.md) | Urgent | Chromium CVE-2026-106414: Improper input validation in Mobile | 9.6 | 0.0034 | | | [CVE-2026-106419](https://patchblox.com/security/data/cve/CVE-2026-106419.md) | Urgent | Chromium CVE-2026-106419: Use after free in ANGLE | 9.6 | 0.0033 | | | [CVE-2026-106323](https://patchblox.com/security/data/cve/CVE-2026-106323.md) | Urgent | chromium: Missing authorization in Chrome for iOS in Google Chrome on on iOS prior to 155.0.8059.39 allowed a remote attacker l... | 9.6 | 0.0033 | | | [CVE-2026-106240](https://patchblox.com/security/data/cve/CVE-2026-106240.md) | High | Chromium CVE-2026-106240: Type confusion | 8.8 | 0.0055 | | | [CVE-2026-106357](https://patchblox.com/security/data/cve/CVE-2026-106357.md) | High | Chromium CVE-2026-106357: Use after free | 8.8 | 0.0052 | | | [CVE-2026-106211](https://patchblox.com/security/data/cve/CVE-2026-106211.md) | High | Chromium CVE-2026-106211: Use after free | 9.6 | 0.0046 | | | [CVE-2026-106227](https://patchblox.com/security/data/cve/CVE-2026-106227.md) | High | Chromium CVE-2026-106227: Use after free | 9.6 | 0.0044 | | | [CVE-2026-106239](https://patchblox.com/security/data/cve/CVE-2026-106239.md) | High | Chromium CVE-2026-106239: Integer overflow | 9.6 | 0.0044 | | | [CVE-2026-106378](https://patchblox.com/security/data/cve/CVE-2026-106378.md) | High | Chromium CVE-2026-106378: Privilege elevation | 8.3 | 0.0041 | | | [CVE-2026-106375](https://patchblox.com/security/data/cve/CVE-2026-106375.md) | High | Chromium CVE-2026-106375: Incomplete cleanup | 9.6 | 0.0041 | | | [CVE-2026-106193](https://patchblox.com/security/data/cve/CVE-2026-106193.md) | High | Chromium CVE-2026-106193: Use after free | 8.8 | 0.0040 | | | [CVE-2026-106194](https://patchblox.com/security/data/cve/CVE-2026-106194.md) | High | Chromium CVE-2026-106194: Missing authorization | 8.3 | 0.0040 | | | [CVE-2026-106268](https://patchblox.com/security/data/cve/CVE-2026-106268.md) | High | Chromium CVE-2026-106268: Use after free | 8.8 | 0.0039 | | | [CVE-2026-106200](https://patchblox.com/security/data/cve/CVE-2026-106200.md) | High | Chromium CVE-2026-106200: Use after free | 8.8 | 0.0039 | | | [CVE-2026-106233](https://patchblox.com/security/data/cve/CVE-2026-106233.md) | High | Chromium CVE-2026-106233: Use after free | 8.3 | 0.0039 | | | [CVE-2026-106235](https://patchblox.com/security/data/cve/CVE-2026-106235.md) | High | Chromium CVE-2026-106235: Use after free | 8.8 | 0.0038 | | | [CVE-2026-106228](https://patchblox.com/security/data/cve/CVE-2026-106228.md) | High | Chromium CVE-2026-106228: Confused deputy | 8.3 | 0.0038 | | | [CVE-2026-106190](https://patchblox.com/security/data/cve/CVE-2026-106190.md) | High | Chromium CVE-2026-106190: Use after free | 8.8 | 0.0037 | | | [CVE-2026-110137](https://patchblox.com/security/data/cve/CVE-2026-110137.md) | High | Chromium CVE-2026-110137: Use after free | 8.8 | 0.0037 | | | [CVE-2026-106191](https://patchblox.com/security/data/cve/CVE-2026-106191.md) | High | Chromium CVE-2026-106191: Missing authorization | 8.3 | 0.0037 | | | [CVE-2026-110916](https://patchblox.com/security/data/cve/CVE-2026-110916.md) | High | Chromium CVE-2026-110916: Improper input validation in Desktop | 9.6 | 0.0036 | | | [CVE-2026-106374](https://patchblox.com/security/data/cve/CVE-2026-106374.md) | High | Chromium CVE-2026-106374: Type confusion | 8.8 | 0.0036 | | | [CVE-2026-106204](https://patchblox.com/security/data/cve/CVE-2026-106204.md) | High | Chromium CVE-2026-106204: Use after free | 8.8 | 0.0036 | | | [CVE-2026-106341](https://patchblox.com/security/data/cve/CVE-2026-106341.md) | High | Chromium CVE-2026-106341: Type confusion | 8.8 | 0.0036 | | | [CVE-2026-106329](https://patchblox.com/security/data/cve/CVE-2026-106329.md) | High | Chromium CVE-2026-106329: Incorrect authorization | 9.6 | 0.0036 | | | [CVE-2026-106203](https://patchblox.com/security/data/cve/CVE-2026-106203.md) | High | Chromium CVE-2026-106203: Incomplete cleanup | 8.8 | 0.0036 | | | [CVE-2026-106281](https://patchblox.com/security/data/cve/CVE-2026-106281.md) | High | Chromium CVE-2026-106281: Use after free | 9.6 | 0.0035 | | | [CVE-2026-106352](https://patchblox.com/security/data/cve/CVE-2026-106352.md) | High | Chromium CVE-2026-106352: Incorrect authorization | 8.8 | 0.0034 | | | [CVE-2026-106212](https://patchblox.com/security/data/cve/CVE-2026-106212.md) | High | Chromium CVE-2026-106212: Incorrect authorization | 8.8 | 0.0034 | | | [CVE-2026-106247](https://patchblox.com/security/data/cve/CVE-2026-106247.md) | High | Chromium CVE-2026-106247: Buffer overflow | 8.8 | 0.0034 | | | [CVE-2026-106401](https://patchblox.com/security/data/cve/CVE-2026-106401.md) | High | Chromium CVE-2026-106401: Out of bounds write | 9.6 | 0.0034 | | | [CVE-2026-106417](https://patchblox.com/security/data/cve/CVE-2026-106417.md) | High | Chromium CVE-2026-106417: Integer overflow | 9.6 | 0.0034 | | | [CVE-2026-106207](https://patchblox.com/security/data/cve/CVE-2026-106207.md) | High | Chromium CVE-2026-106207: Race condition | 8.8 | 0.0034 | | | [CVE-2026-106383](https://patchblox.com/security/data/cve/CVE-2026-106383.md) | High | Chromium CVE-2026-106383: Use after free | 8.8 | 0.0034 | | | [CVE-2026-106292](https://patchblox.com/security/data/cve/CVE-2026-106292.md) | High | Chromium CVE-2026-106292: Buffer overflow | 8.3 | 0.0033 | | | [CVE-2026-106335](https://patchblox.com/security/data/cve/CVE-2026-106335.md) | High | Chromium CVE-2026-106335: Use after free | 8.8 | 0.0033 | | | [CVE-2026-106346](https://patchblox.com/security/data/cve/CVE-2026-106346.md) | High | Chromium CVE-2026-106346: Improper state validation | 8.8 | 0.0033 | | | [CVE-2026-106349](https://patchblox.com/security/data/cve/CVE-2026-106349.md) | High | Chromium CVE-2026-106349: Use after free | 8.8 | 0.0033 | | | [CVE-2026-106241](https://patchblox.com/security/data/cve/CVE-2026-106241.md) | High | Chromium CVE-2026-106241: Incorrect authorization | 9.6 | 0.0033 | | | [CVE-2026-110155](https://patchblox.com/security/data/cve/CVE-2026-110155.md) | High | Chromium CVE-2026-110155: Buffer overflow | 8.8 | 0.0033 | | | [CVE-2026-110142](https://patchblox.com/security/data/cve/CVE-2026-110142.md) | High | Chromium CVE-2026-110142: Use after free | 9.6 | 0.0033 | | | [CVE-2026-106220](https://patchblox.com/security/data/cve/CVE-2026-106220.md) | High | Chromium CVE-2026-106220: Information leak | 8.8 | 0.0033 | | | [CVE-2026-110913](https://patchblox.com/security/data/cve/CVE-2026-110913.md) | High | Chromium CVE-2026-110913: Memory corruption in DOM | 8.8 | 0.0033 | | | [CVE-2026-106293](https://patchblox.com/security/data/cve/CVE-2026-106293.md) | High | Chromium CVE-2026-106293: Type confusion | 8.8 | 0.0032 | | | [CVE-2026-106225](https://patchblox.com/security/data/cve/CVE-2026-106225.md) | High | Chromium CVE-2026-106225: Missing authorization | 8.8 | 0.0032 | | | [CVE-2026-106234](https://patchblox.com/security/data/cve/CVE-2026-106234.md) | High | Chromium CVE-2026-106234: Use after free | 9.6 | 0.0032 | | | [CVE-2026-106387](https://patchblox.com/security/data/cve/CVE-2026-106387.md) | High | Chromium CVE-2026-106387: Missing authorization in Mobile | 8.8 | 0.0032 | | | [CVE-2026-106195](https://patchblox.com/security/data/cve/CVE-2026-106195.md) | High | Chromium CVE-2026-106195: Incorrect authorization | 9.1 | 0.0032 | | | [CVE-2026-106373](https://patchblox.com/security/data/cve/CVE-2026-106373.md) | High | Chromium CVE-2026-106373: Use after free | 8.8 | 0.0032 | | | [CVE-2026-110140](https://patchblox.com/security/data/cve/CVE-2026-110140.md) | High | Chromium CVE-2026-110140: Type confusion | 8.8 | 0.0032 | | | [CVE-2026-110157](https://patchblox.com/security/data/cve/CVE-2026-110157.md) | High | Chromium CVE-2026-110157: Use after free | 8.8 | 0.0032 | | | [CVE-2026-110162](https://patchblox.com/security/data/cve/CVE-2026-110162.md) | High | Chromium CVE-2026-110162: Use after free | 8.8 | 0.0032 | | | [CVE-2026-110163](https://patchblox.com/security/data/cve/CVE-2026-110163.md) | High | Chromium CVE-2026-110163: Use after free | 8.8 | 0.0032 | | | [CVE-2026-106221](https://patchblox.com/security/data/cve/CVE-2026-106221.md) | High | Chromium CVE-2026-106221: Confused deputy in WebAPKs | 8.3 | 0.0031 | | | [CVE-2026-110158](https://patchblox.com/security/data/cve/CVE-2026-110158.md) | High | Chromium CVE-2026-110158: Use after free in Passwords | 8.3 | 0.0031 | | | [CVE-2026-106294](https://patchblox.com/security/data/cve/CVE-2026-106294.md) | High | Chromium CVE-2026-106294: Incomplete cleanup | 9.1 | 0.0031 | | | [CVE-2026-106201](https://patchblox.com/security/data/cve/CVE-2026-106201.md) | High | Chromium CVE-2026-106201: Race condition | 8.8 | 0.0031 | | | [CVE-2026-106269](https://patchblox.com/security/data/cve/CVE-2026-106269.md) | High | Chromium CVE-2026-106269: Use after free | 8.8 | 0.0031 | | | [CVE-2026-106278](https://patchblox.com/security/data/cve/CVE-2026-106278.md) | High | Chromium CVE-2026-106278: Use after free | 8.8 | 0.0031 | | | [CVE-2026-106283](https://patchblox.com/security/data/cve/CVE-2026-106283.md) | High | Chromium CVE-2026-106283: Use after free | 8.8 | 0.0031 | | | [CVE-2026-106411](https://patchblox.com/security/data/cve/CVE-2026-106411.md) | High | Chromium CVE-2026-106411: Use after free | 8.8 | 0.0031 | | | [CVE-2026-106421](https://patchblox.com/security/data/cve/CVE-2026-106421.md) | High | Chromium CVE-2026-106421: Use after free | 8.8 | 0.0031 | | | [CVE-2026-106423](https://patchblox.com/security/data/cve/CVE-2026-106423.md) | High | Chromium CVE-2026-106423: Use after free | 8.8 | 0.0031 | | | [CVE-2026-110147](https://patchblox.com/security/data/cve/CVE-2026-110147.md) | High | Chromium CVE-2026-110147: Use after free | 8.8 | 0.0031 | | | [CVE-2026-106342](https://patchblox.com/security/data/cve/CVE-2026-106342.md) | High | Chromium CVE-2026-106342: Information leak | 8.8 | 0.0031 | | | [CVE-2026-106238](https://patchblox.com/security/data/cve/CVE-2026-106238.md) | High | Chromium CVE-2026-106238: Race condition | 8.3 | 0.0030 | | | [CVE-2026-106248](https://patchblox.com/security/data/cve/CVE-2026-106248.md) | High | Chromium CVE-2026-106248: Use after free | 8.8 | 0.0030 | | | [CVE-2026-106252](https://patchblox.com/security/data/cve/CVE-2026-106252.md) | High | Chromium CVE-2026-106252: Incorrect comparison | 8.8 | 0.0030 | | | [CVE-2026-106257](https://patchblox.com/security/data/cve/CVE-2026-106257.md) | High | Chromium CVE-2026-106257: Use after free | 8.8 | 0.0030 | | | [CVE-2026-106291](https://patchblox.com/security/data/cve/CVE-2026-106291.md) | High | Chromium CVE-2026-106291: Use after free | 8.8 | 0.0030 | | | [CVE-2026-106315](https://patchblox.com/security/data/cve/CVE-2026-106315.md) | High | Chromium CVE-2026-106315: Use after free | 8.8 | 0.0030 | | | [CVE-2026-106318](https://patchblox.com/security/data/cve/CVE-2026-106318.md) | High | Chromium CVE-2026-106318: Use after free | 8.8 | 0.0030 | | | [CVE-2026-110914](https://patchblox.com/security/data/cve/CVE-2026-110914.md) | High | Chromium CVE-2026-110914: Memory corruption in Workers | 8.8 | 0.0030 | | | [CVE-2026-110915](https://patchblox.com/security/data/cve/CVE-2026-110915.md) | High | Chromium CVE-2026-110915: Use after free in Compositing | 8.8 | 0.0030 | | | [CVE-2026-106393](https://patchblox.com/security/data/cve/CVE-2026-106393.md) | High | Chromium CVE-2026-106393: Use after free | 8.3 | 0.0030 | | | [CVE-2026-106205](https://patchblox.com/security/data/cve/CVE-2026-106205.md) | High | Chromium CVE-2026-106205: Missing authorization | 8.1 | 0.0030 | | | [CVE-2026-110166](https://patchblox.com/security/data/cve/CVE-2026-110166.md) | High | Chromium CVE-2026-110166: Buffer overflow | 8.8 | 0.0030 | | | [CVE-2026-106363](https://patchblox.com/security/data/cve/CVE-2026-106363.md) | High | Chromium CVE-2026-106363: Missing authorization | 8.3 | 0.0030 | | | [CVE-2026-110139](https://patchblox.com/security/data/cve/CVE-2026-110139.md) | High | Chromium CVE-2026-110139: Use after free | 8.8 | 0.0029 | | | [CVE-2026-110153](https://patchblox.com/security/data/cve/CVE-2026-110153.md) | High | Chromium CVE-2026-110153: Use after free | 8.8 | 0.0029 | | | [CVE-2026-110154](https://patchblox.com/security/data/cve/CVE-2026-110154.md) | High | Chromium CVE-2026-110154: Use after free | 8.8 | 0.0029 | | | [CVE-2026-106189](https://patchblox.com/security/data/cve/CVE-2026-106189.md) | High | Chromium CVE-2026-106189: Code injection | 7.3 | 0.0029 | | | [CVE-2026-110156](https://patchblox.com/security/data/cve/CVE-2026-110156.md) | High | Chromium CVE-2026-110156: Incorrect reference resolution | 8.3 | 0.0029 | | | [CVE-2026-110138](https://patchblox.com/security/data/cve/CVE-2026-110138.md) | High | Chromium CVE-2026-110138: Use after free | 8.3 | 0.0028 | | | [CVE-2026-110145](https://patchblox.com/security/data/cve/CVE-2026-110145.md) | High | Chromium CVE-2026-110145: Use after free | 8.3 | 0.0028 | | | [CVE-2026-106274](https://patchblox.com/security/data/cve/CVE-2026-106274.md) | High | Chromium CVE-2026-106274: Incorrect reference resolution | 8.8 | 0.0028 | | | [CVE-2026-106308](https://patchblox.com/security/data/cve/CVE-2026-106308.md) | High | Chromium CVE-2026-106308: Incorrect reference resolution | 8.8 | 0.0028 | | | [CVE-2026-106334](https://patchblox.com/security/data/cve/CVE-2026-106334.md) | High | Chromium CVE-2026-106334: Information leak | 8.8 | 0.0028 | | | [CVE-2026-106350](https://patchblox.com/security/data/cve/CVE-2026-106350.md) | High | Chromium CVE-2026-106350: Incorrect authorization | 8.8 | 0.0028 | | | [CVE-2026-106198](https://patchblox.com/security/data/cve/CVE-2026-106198.md) | High | Chromium CVE-2026-106198: Missing authorization | 8.2 | 0.0027 | | | [CVE-2026-106409](https://patchblox.com/security/data/cve/CVE-2026-106409.md) | High | Chromium CVE-2026-106409: Incorrect reference resolution | 8.3 | 0.0027 | | | [CVE-2026-110164](https://patchblox.com/security/data/cve/CVE-2026-110164.md) | High | Chromium CVE-2026-110164: Use after free | 8.8 | 0.0026 | | | [CVE-2026-110167](https://patchblox.com/security/data/cve/CVE-2026-110167.md) | High | Chromium CVE-2026-110167: Use after free | 8.8 | 0.0026 | | | [CVE-2026-110168](https://patchblox.com/security/data/cve/CVE-2026-110168.md) | High | Chromium CVE-2026-110168: Use after free | 8.8 | 0.0026 | | | [CVE-2026-110169](https://patchblox.com/security/data/cve/CVE-2026-110169.md) | High | Chromium CVE-2026-110169: Use after free | 8.8 | 0.0026 | | | [CVE-2026-110171](https://patchblox.com/security/data/cve/CVE-2026-110171.md) | High | Chromium CVE-2026-110171: Use after free | 8.8 | 0.0026 | | | [CVE-2026-110172](https://patchblox.com/security/data/cve/CVE-2026-110172.md) | High | Chromium CVE-2026-110172: Use after free | 8.8 | 0.0026 | | | [CVE-2026-106377](https://patchblox.com/security/data/cve/CVE-2026-106377.md) | High | Chromium CVE-2026-106377: Race condition | 8.3 | 0.0026 | | | [CVE-2026-106256](https://patchblox.com/security/data/cve/CVE-2026-106256.md) | High | Chromium CVE-2026-106256: Information leak | 8.8 | 0.0026 | | | [CVE-2026-106196](https://patchblox.com/security/data/cve/CVE-2026-106196.md) | High | Chromium CVE-2026-106196: Missing authorization | 7.6 | 0.0026 | | | [CVE-2026-106199](https://patchblox.com/security/data/cve/CVE-2026-106199.md) | High | Chromium CVE-2026-106199: Incorrect authorization | 8.2 | 0.0025 | | | [CVE-2026-110919](https://patchblox.com/security/data/cve/CVE-2026-110919.md) | High | Chromium CVE-2026-110919: Use after free in V8 | 8.8 | 0.0025 | | | [CVE-2026-110920](https://patchblox.com/security/data/cve/CVE-2026-110920.md) | High | Chromium CVE-2026-110920: Memory corruption in V8 | 8.8 | 0.0025 | | | [CVE-2026-110921](https://patchblox.com/security/data/cve/CVE-2026-110921.md) | High | Chromium CVE-2026-110921: Use after free in V8 | 8.8 | 0.0025 | | | [CVE-2026-106309](https://patchblox.com/security/data/cve/CVE-2026-106309.md) | High | Chromium CVE-2026-106309: Incorrect authorization | 8.8 | 0.0025 | | | [CVE-2026-106371](https://patchblox.com/security/data/cve/CVE-2026-106371.md) | High | Chromium CVE-2026-106371: Incorrect authorization | 8.8 | 0.0025 | | | [CVE-2026-106237](https://patchblox.com/security/data/cve/CVE-2026-106237.md) | High | Chromium CVE-2026-106237: Information leak | 9.6 | 0.0025 | | | [CVE-2026-110159](https://patchblox.com/security/data/cve/CVE-2026-110159.md) | High | Chromium CVE-2026-110159: Incorrect authorization | 9.6 | 0.0024 | | | [CVE-2026-106249](https://patchblox.com/security/data/cve/CVE-2026-106249.md) | High | Chromium CVE-2026-106249: Incorrect authorization | 8.8 | 0.0024 | | | [CVE-2026-106314](https://patchblox.com/security/data/cve/CVE-2026-106314.md) | High | Chromium CVE-2026-106314: Incorrect authorization | 8.8 | 0.0024 | | | [CVE-2026-106255](https://patchblox.com/security/data/cve/CVE-2026-106255.md) | High | Chromium CVE-2026-106255: Race condition | 8.8 | 0.0024 | | | [CVE-2026-106301](https://patchblox.com/security/data/cve/CVE-2026-106301.md) | High | Chromium CVE-2026-106301: Confused deputy | 8.1 | 0.0024 | | | [CVE-2026-106403](https://patchblox.com/security/data/cve/CVE-2026-106403.md) | High | Chromium CVE-2026-106403: Incorrect authorization | 8.1 | 0.0024 | | | [CVE-2026-106412](https://patchblox.com/security/data/cve/CVE-2026-106412.md) | High | Chromium CVE-2026-106412: Race condition | 8.3 | 0.0024 | | | [CVE-2026-106426](https://patchblox.com/security/data/cve/CVE-2026-106426.md) | High | Chromium CVE-2026-106426: Race condition | 8.3 | 0.0023 | | | [CVE-2026-106271](https://patchblox.com/security/data/cve/CVE-2026-106271.md) | High | Chromium CVE-2026-106271: Missing authorization | 8.1 | 0.0023 | | | [CVE-2026-106188](https://patchblox.com/security/data/cve/CVE-2026-106188.md) | High | Chromium CVE-2026-106188: Confused deputy | 7.1 | 0.0023 | | | [CVE-2026-106379](https://patchblox.com/security/data/cve/CVE-2026-106379.md) | High | Chromium CVE-2026-106379: Uninitialized resource | 9.6 | 0.0022 | | | [CVE-2026-106245](https://patchblox.com/security/data/cve/CVE-2026-106245.md) | High | Chromium CVE-2026-106245: Uninitialized resource | 8.8 | 0.0022 | | | [CVE-2026-106304](https://patchblox.com/security/data/cve/CVE-2026-106304.md) | High | Chromium CVE-2026-106304: Out of bounds read | 8.8 | 0.0020 | | | [CVE-2026-110144](https://patchblox.com/security/data/cve/CVE-2026-110144.md) | High | Chromium CVE-2026-110144: Incorrect authorization | 9.6 | 0.0020 | | | [CVE-2026-106186](https://patchblox.com/security/data/cve/CVE-2026-106186.md) | High | Chromium CVE-2026-106186: Uncontrolled search path element | 8.6 | 0.0016 | | | [CVE-2026-106399](https://patchblox.com/security/data/cve/CVE-2026-106399.md) | High | Chromium CVE-2026-106399: Out of bounds read | 9.6 | 0.0010 | | | [CVE-2026-106279](https://patchblox.com/security/data/cve/CVE-2026-106279.md) | High | Chromium CVE-2026-106279: Incorrect reference resolution | 7.4 | 0.0009 | | | [CVE-2026-106367](https://patchblox.com/security/data/cve/CVE-2026-106367.md) | High | Chromium CVE-2026-106367: Missing authorization in Mobile | 8.4 | 0.0009 | | | [CVE-2026-106386](https://patchblox.com/security/data/cve/CVE-2026-106386.md) | Routine | Chromium CVE-2026-106386: Uninitialized resource | 6.5 | 0.0033 | | | [CVE-2026-106206](https://patchblox.com/security/data/cve/CVE-2026-106206.md) | Routine | Chromium CVE-2026-106206: Improper input validation in Mobile | 5.9 | 0.0031 | | | [CVE-2026-106181](https://patchblox.com/security/data/cve/CVE-2026-106181.md) | Routine | Chromium CVE-2026-106181: Incorrect reference resolution | 5.3 | 0.0030 | | | [CVE-2026-106230](https://patchblox.com/security/data/cve/CVE-2026-106230.md) | Routine | Chromium CVE-2026-106230: Incorrect reference resolution | 5.3 | 0.0030 | | | [CVE-2026-106215](https://patchblox.com/security/data/cve/CVE-2026-106215.md) | Routine | Chromium CVE-2026-106215: Uninitialized resource | 4.7 | 0.0028 | | | [CVE-2026-106223](https://patchblox.com/security/data/cve/CVE-2026-106223.md) | Routine | Chromium CVE-2026-106223: Uninitialized resource in GPU | 4.7 | 0.0028 | | | [CVE-2026-106361](https://patchblox.com/security/data/cve/CVE-2026-106361.md) | Routine | Chromium CVE-2026-106361: Incorrect provision of specified functionality in Mobile | 6.5 | 0.0028 | | | [CVE-2026-106183](https://patchblox.com/security/data/cve/CVE-2026-106183.md) | Routine | Chromium CVE-2026-106183: Missing authorization | 5.9 | 0.0028 | | | [CVE-2026-106222](https://patchblox.com/security/data/cve/CVE-2026-106222.md) | Routine | Chromium CVE-2026-106222: Incorrect authorization | 5.9 | 0.0028 | | | [CVE-2026-106185](https://patchblox.com/security/data/cve/CVE-2026-106185.md) | Routine | Chromium CVE-2026-106185: Improper input validation | 6.5 | 0.0028 | | | [CVE-2026-106362](https://patchblox.com/security/data/cve/CVE-2026-106362.md) | Routine | Chromium CVE-2026-106362: Missing authorization | 6.5 | 0.0028 | | | [CVE-2026-106355](https://patchblox.com/security/data/cve/CVE-2026-106355.md) | Routine | Chromium CVE-2026-106355: Missing authorization | 5.3 | 0.0027 | | | [CVE-2026-106202](https://patchblox.com/security/data/cve/CVE-2026-106202.md) | Routine | Chromium CVE-2026-106202: Uninitialized resource | 4.7 | 0.0027 | | | [CVE-2026-106184](https://patchblox.com/security/data/cve/CVE-2026-106184.md) | Routine | Chromium CVE-2026-106184: Uninitialized resource | 4.3 | 0.0027 | | | [CVE-2026-106348](https://patchblox.com/security/data/cve/CVE-2026-106348.md) | Routine | Chromium CVE-2026-106348: Information leak | 6.5 | 0.0026 | | | [CVE-2026-106231](https://patchblox.com/security/data/cve/CVE-2026-106231.md) | Routine | Chromium CVE-2026-106231: Uninitialized resource | 4.7 | 0.0026 | | | [CVE-2026-106359](https://patchblox.com/security/data/cve/CVE-2026-106359.md) | Routine | Chromium CVE-2026-106359: Confused deputy | 4.3 | 0.0026 | | | [CVE-2026-106209](https://patchblox.com/security/data/cve/CVE-2026-106209.md) | Routine | Chromium CVE-2026-106209: UI misrepresentation in Mobile | 5.4 | 0.0026 | | | [CVE-2026-106360](https://patchblox.com/security/data/cve/CVE-2026-106360.md) | Routine | Chromium CVE-2026-106360: Information leak | 4.3 | 0.0025 | | | [CVE-2026-106365](https://patchblox.com/security/data/cve/CVE-2026-106365.md) | Routine | Chromium CVE-2026-106365: Missing authorization | 6.5 | 0.0025 | | | [CVE-2026-106381](https://patchblox.com/security/data/cve/CVE-2026-106381.md) | Routine | Chromium CVE-2026-106381: Incorrect authorization | 6.5 | 0.0025 | | | [CVE-2026-106229](https://patchblox.com/security/data/cve/CVE-2026-106229.md) | Routine | Chromium CVE-2026-106229: UI misrepresentation | 5.4 | 0.0025 | | | [CVE-2026-106261](https://patchblox.com/security/data/cve/CVE-2026-106261.md) | Routine | Chromium CVE-2026-106261: Uninitialized resource | 6.5 | 0.0025 | | | [CVE-2026-106179](https://patchblox.com/security/data/cve/CVE-2026-106179.md) | Routine | Chromium CVE-2026-106179: UI misrepresentation | 5.4 | 0.0025 | | | [CVE-2026-106182](https://patchblox.com/security/data/cve/CVE-2026-106182.md) | Routine | Chromium CVE-2026-106182: UI misrepresentation | 5.4 | 0.0025 | | | [CVE-2026-106232](https://patchblox.com/security/data/cve/CVE-2026-106232.md) | Routine | Chromium CVE-2026-106232: UI misrepresentation | 5.4 | 0.0025 | | | [CVE-2026-106356](https://patchblox.com/security/data/cve/CVE-2026-106356.md) | Routine | Chromium CVE-2026-106356: Clickjacking | 5.4 | 0.0025 | | | [CVE-2026-106217](https://patchblox.com/security/data/cve/CVE-2026-106217.md) | Routine | Chromium CVE-2026-106217: Missing authorization | 4.3 | 0.0024 | | | [CVE-2026-110146](https://patchblox.com/security/data/cve/CVE-2026-110146.md) | Routine | Chromium CVE-2026-110146: Information leak | 6.5 | 0.0024 | | | [CVE-2026-106384](https://patchblox.com/security/data/cve/CVE-2026-106384.md) | Routine | Chromium CVE-2026-106384: Missing authorization | 6.5 | 0.0024 | | | [CVE-2026-106208](https://patchblox.com/security/data/cve/CVE-2026-106208.md) | Routine | Chromium CVE-2026-106208: Missing authorization | 6.1 | 0.0024 | | | [CVE-2026-106325](https://patchblox.com/security/data/cve/CVE-2026-106325.md) | Routine | Chromium CVE-2026-106325: Incorrect reference resolution | 4.3 | 0.0023 | | | [CVE-2026-106310](https://patchblox.com/security/data/cve/CVE-2026-106310.md) | Routine | Chromium CVE-2026-106310: Use of released resource | 6.5 | 0.0023 | | | [CVE-2026-106226](https://patchblox.com/security/data/cve/CVE-2026-106226.md) | Routine | Chromium CVE-2026-106226: Improper input validation | 4.2 | 0.0023 | | | [CVE-2026-106266](https://patchblox.com/security/data/cve/CVE-2026-106266.md) | Routine | Chromium CVE-2026-106266: Confused deputy | 6.5 | 0.0023 | | | [CVE-2026-106280](https://patchblox.com/security/data/cve/CVE-2026-106280.md) | Routine | Chromium CVE-2026-106280: Incorrect authorization | 6.5 | 0.0023 | | | [CVE-2026-106289](https://patchblox.com/security/data/cve/CVE-2026-106289.md) | Routine | Chromium CVE-2026-106289: Missing authorization | 6.5 | 0.0023 | | | [CVE-2026-106264](https://patchblox.com/security/data/cve/CVE-2026-106264.md) | Routine | Chromium CVE-2026-106264: Missing authorization | 5.4 | 0.0023 | | | [CVE-2026-106242](https://patchblox.com/security/data/cve/CVE-2026-106242.md) | Routine | Chromium CVE-2026-106242: Information leak | 6.5 | 0.0023 | | | [CVE-2026-106236](https://patchblox.com/security/data/cve/CVE-2026-106236.md) | Routine | Chromium CVE-2026-106236: UI misrepresentation | 5.4 | 0.0023 | | | [CVE-2026-106331](https://patchblox.com/security/data/cve/CVE-2026-106331.md) | Routine | Chromium CVE-2026-106331: Improper input validation | 6.5 | 0.0023 | | | [CVE-2026-106353](https://patchblox.com/security/data/cve/CVE-2026-106353.md) | Routine | Chromium CVE-2026-106353: Improper input validation in Mobile | 6.5 | 0.0023 | | | [CVE-2026-106273](https://patchblox.com/security/data/cve/CVE-2026-106273.md) | Routine | Chromium CVE-2026-106273: Uninitialized resource | 4.7 | 0.0023 | | | [CVE-2026-106408](https://patchblox.com/security/data/cve/CVE-2026-106408.md) | Routine | Chromium CVE-2026-106408: Protection mechanism failure in Mobile | 6.5 | 0.0023 | | | [CVE-2026-106388](https://patchblox.com/security/data/cve/CVE-2026-106388.md) | Routine | Chromium CVE-2026-106388: Missing authorization | 5.3 | 0.0023 | | | [CVE-2026-106180](https://patchblox.com/security/data/cve/CVE-2026-106180.md) | Routine | Chromium CVE-2026-106180: Observable discrepancy | 3.1 | 0.0022 | | | [CVE-2026-106312](https://patchblox.com/security/data/cve/CVE-2026-106312.md) | Routine | Chromium CVE-2026-106312: Missing authorization | 6.5 | 0.0022 | | | [CVE-2026-106258](https://patchblox.com/security/data/cve/CVE-2026-106258.md) | Routine | Chromium CVE-2026-106258: Uninitialized resource | 4.7 | 0.0022 | | | [CVE-2026-106275](https://patchblox.com/security/data/cve/CVE-2026-106275.md) | Routine | Chromium CVE-2026-106275: Uninitialized resource | 4.7 | 0.0022 | | | [CVE-2026-106290](https://patchblox.com/security/data/cve/CVE-2026-106290.md) | Routine | Chromium CVE-2026-106290: Uninitialized resource in GPU | 4.7 | 0.0022 | | | [CVE-2026-106370](https://patchblox.com/security/data/cve/CVE-2026-106370.md) | Routine | Chromium CVE-2026-106370: Uninitialized resource | 4.7 | 0.0022 | | | [CVE-2026-106376](https://patchblox.com/security/data/cve/CVE-2026-106376.md) | Routine | Chromium CVE-2026-106376: Uninitialized resource | 4.7 | 0.0022 | | | [CVE-2026-106394](https://patchblox.com/security/data/cve/CVE-2026-106394.md) | Routine | Chromium CVE-2026-106394: Incomplete cleanup | 4.3 | 0.0022 | | | [CVE-2026-106267](https://patchblox.com/security/data/cve/CVE-2026-106267.md) | Routine | Chromium CVE-2026-106267: Missing authorization | 6.5 | 0.0022 | | | [CVE-2026-106389](https://patchblox.com/security/data/cve/CVE-2026-106389.md) | Routine | Chromium CVE-2026-106389: Incorrect authorization | 6.5 | 0.0022 | | | [CVE-2026-106354](https://patchblox.com/security/data/cve/CVE-2026-106354.md) | Routine | Chromium CVE-2026-106354: Improper resource exposure | 4.3 | 0.0022 | | | [CVE-2026-106307](https://patchblox.com/security/data/cve/CVE-2026-106307.md) | Routine | Chromium CVE-2026-106307: Incorrect authorization | 6.5 | 0.0022 | | | [CVE-2026-106407](https://patchblox.com/security/data/cve/CVE-2026-106407.md) | Routine | Chromium CVE-2026-106407: Incorrect authorization | 6.5 | 0.0022 | | | [CVE-2026-106366](https://patchblox.com/security/data/cve/CVE-2026-106366.md) | Routine | Chromium CVE-2026-106366: Incomplete cleanup in CustomTabs | 5.4 | 0.0022 | | | [CVE-2026-106364](https://patchblox.com/security/data/cve/CVE-2026-106364.md) | Routine | Chromium CVE-2026-106364: Incorrect authorization | 5.3 | 0.0022 | | | [CVE-2026-106224](https://patchblox.com/security/data/cve/CVE-2026-106224.md) | Routine | Chromium CVE-2026-106224: Missing authorization | 3.1 | 0.0022 | | | [CVE-2026-106332](https://patchblox.com/security/data/cve/CVE-2026-106332.md) | Routine | Chromium CVE-2026-106332: Integer overflow | 4.3 | 0.0021 | | | [CVE-2026-106345](https://patchblox.com/security/data/cve/CVE-2026-106345.md) | Routine | Chromium CVE-2026-106345: Use of released resource | 4.2 | 0.0021 | | | [CVE-2026-106210](https://patchblox.com/security/data/cve/CVE-2026-106210.md) | Routine | Chromium CVE-2026-106210: Observable discrepancy | 3.1 | 0.0021 | | | [CVE-2026-106286](https://patchblox.com/security/data/cve/CVE-2026-106286.md) | Routine | Chromium CVE-2026-106286: Confused deputy | 6.5 | 0.0021 | | | [CVE-2026-106418](https://patchblox.com/security/data/cve/CVE-2026-106418.md) | Routine | Chromium CVE-2026-106418: Missing authorization | 6.5 | 0.0021 | | | [CVE-2026-106302](https://patchblox.com/security/data/cve/CVE-2026-106302.md) | Routine | Chromium CVE-2026-106302: UI misrepresentation | 5.4 | 0.0021 | | | [CVE-2026-106380](https://patchblox.com/security/data/cve/CVE-2026-106380.md) | Routine | Chromium CVE-2026-106380: UI misrepresentation in UI | 5.4 | 0.0021 | | | [CVE-2026-106303](https://patchblox.com/security/data/cve/CVE-2026-106303.md) | Routine | Chromium CVE-2026-106303: Observable discrepancy | 5.3 | 0.0021 | | | [CVE-2026-106351](https://patchblox.com/security/data/cve/CVE-2026-106351.md) | Routine | Chromium CVE-2026-106351: Observable discrepancy | 5.3 | 0.0021 | | | [CVE-2026-106395](https://patchblox.com/security/data/cve/CVE-2026-106395.md) | Routine | Chromium CVE-2026-106395: Uninitialized resource in Dawn | 4.7 | 0.0021 | | | [CVE-2026-106187](https://patchblox.com/security/data/cve/CVE-2026-106187.md) | Routine | Chromium CVE-2026-106187: Missing authorization | 4.2 | 0.0021 | | | [CVE-2026-106263](https://patchblox.com/security/data/cve/CVE-2026-106263.md) | Routine | Chromium CVE-2026-106263: Improper input validation | 6.5 | 0.0021 | | | [CVE-2026-106404](https://patchblox.com/security/data/cve/CVE-2026-106404.md) | Routine | Chromium CVE-2026-106404: Incorrect authorization | 6.5 | 0.0021 | | | [CVE-2026-106213](https://patchblox.com/security/data/cve/CVE-2026-106213.md) | Routine | Chromium CVE-2026-106213: Race condition | 4.3 | 0.0021 | | | [CVE-2026-106287](https://patchblox.com/security/data/cve/CVE-2026-106287.md) | Routine | Chromium CVE-2026-106287: Information loss | 4.3 | 0.0020 | | | [CVE-2026-106246](https://patchblox.com/security/data/cve/CVE-2026-106246.md) | Routine | Chromium CVE-2026-106246: Incorrect authorization | 5.4 | 0.0020 | | | [CVE-2026-106270](https://patchblox.com/security/data/cve/CVE-2026-106270.md) | Routine | Chromium CVE-2026-106270: Incorrect authorization | 5.4 | 0.0020 | | | [CVE-2026-106284](https://patchblox.com/security/data/cve/CVE-2026-106284.md) | Routine | Chromium CVE-2026-106284: Out of bounds read | 4.7 | 0.0020 | | | [CVE-2026-106277](https://patchblox.com/security/data/cve/CVE-2026-106277.md) | Routine | Chromium CVE-2026-106277: Information leak | 4.3 | 0.0020 | | | [CVE-2026-106336](https://patchblox.com/security/data/cve/CVE-2026-106336.md) | Routine | Chromium CVE-2026-106336: Observable discrepancy | 4.3 | 0.0020 | | | [CVE-2026-106390](https://patchblox.com/security/data/cve/CVE-2026-106390.md) | Routine | Chromium CVE-2026-106390: Incorrect provision of specified functionality | 4.3 | 0.0020 | | | [CVE-2026-106392](https://patchblox.com/security/data/cve/CVE-2026-106392.md) | Routine | Chromium CVE-2026-106392: Information leak | 4.3 | 0.0020 | | | [CVE-2026-106415](https://patchblox.com/security/data/cve/CVE-2026-106415.md) | Routine | Chromium CVE-2026-106415: Information leak | 4.3 | 0.0020 | | | [CVE-2026-110917](https://patchblox.com/security/data/cve/CVE-2026-110917.md) | Routine | Chromium CVE-2026-110917: Memory corruption in SVG | 4.3 | 0.0020 | | | [CVE-2026-110918](https://patchblox.com/security/data/cve/CVE-2026-110918.md) | Routine | Chromium CVE-2026-110918: Memory corruption in Core | 4.3 | 0.0020 | | | [CVE-2026-106402](https://patchblox.com/security/data/cve/CVE-2026-106402.md) | Routine | Chromium CVE-2026-106402: Incorrect authorization | 4.8 | 0.0020 | | | [CVE-2026-106285](https://patchblox.com/security/data/cve/CVE-2026-106285.md) | Routine | Chromium CVE-2026-106285: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-106297](https://patchblox.com/security/data/cve/CVE-2026-106297.md) | Routine | Chromium CVE-2026-106297: Incorrect authorization | 4.3 | 0.0020 | | | [CVE-2026-106422](https://patchblox.com/security/data/cve/CVE-2026-106422.md) | Routine | Chromium CVE-2026-106422: Incorrect authorization | 4.3 | 0.0020 | | | [CVE-2026-106265](https://patchblox.com/security/data/cve/CVE-2026-106265.md) | Routine | Chromium CVE-2026-106265: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-106276](https://patchblox.com/security/data/cve/CVE-2026-106276.md) | Routine | Chromium CVE-2026-106276: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-106282](https://patchblox.com/security/data/cve/CVE-2026-106282.md) | Routine | Chromium CVE-2026-106282: UI misrepresentation in WebOTP | 5.4 | 0.0020 | | | [CVE-2026-106305](https://patchblox.com/security/data/cve/CVE-2026-106305.md) | Routine | Chromium CVE-2026-106305: UI misrepresentation in Mobile | 5.4 | 0.0020 | | | [CVE-2026-106317](https://patchblox.com/security/data/cve/CVE-2026-106317.md) | Routine | Chromium CVE-2026-106317: UI misrepresentation in FullScreen | 5.4 | 0.0020 | | | [CVE-2026-106338](https://patchblox.com/security/data/cve/CVE-2026-106338.md) | Routine | Chromium CVE-2026-106338: UI misrepresentation | 5.4 | 0.0020 | | | [CVE-2026-106343](https://patchblox.com/security/data/cve/CVE-2026-106343.md) | Routine | Chromium CVE-2026-106343: Improper state validation | 5.4 | 0.0020 | | | [CVE-2026-106368](https://patchblox.com/security/data/cve/CVE-2026-106368.md) | Routine | Chromium CVE-2026-106368: UI misrepresentation in UI | 5.4 | 0.0020 | | | [CVE-2026-106333](https://patchblox.com/security/data/cve/CVE-2026-106333.md) | Routine | Chromium CVE-2026-106333: Incorrect authorization | 5.4 | 0.0020 | | | [CVE-2026-106260](https://patchblox.com/security/data/cve/CVE-2026-106260.md) | Routine | Chromium CVE-2026-106260: Incorrect authorization | 4.3 | 0.0019 | | | [CVE-2026-106321](https://patchblox.com/security/data/cve/CVE-2026-106321.md) | Routine | Chromium CVE-2026-106321: Information leak | 4.3 | 0.0019 | | | [CVE-2026-106330](https://patchblox.com/security/data/cve/CVE-2026-106330.md) | Routine | Chromium CVE-2026-106330: Information leak | 4.3 | 0.0019 | | | [CVE-2026-106398](https://patchblox.com/security/data/cve/CVE-2026-106398.md) | Routine | Chromium CVE-2026-106398: Incorrect authorization | 4.3 | 0.0019 | | | [CVE-2026-106214](https://patchblox.com/security/data/cve/CVE-2026-106214.md) | Routine | Chromium CVE-2026-106214: Information leak | 5.3 | 0.0019 | | | [CVE-2026-106327](https://patchblox.com/security/data/cve/CVE-2026-106327.md) | Routine | Chromium CVE-2026-106327: Incorrect authorization | 6.1 | 0.0019 | | | [CVE-2026-106311](https://patchblox.com/security/data/cve/CVE-2026-106311.md) | Routine | Chromium CVE-2026-106311: Clickjacking | 5.4 | 0.0019 | | | [CVE-2026-106406](https://patchblox.com/security/data/cve/CVE-2026-106406.md) | Routine | Chromium CVE-2026-106406: Missing authorization in Mobile | 5.4 | 0.0019 | | | [CVE-2026-106424](https://patchblox.com/security/data/cve/CVE-2026-106424.md) | Routine | Chromium CVE-2026-106424: Information leak | 4.0 | 0.0019 | | | [CVE-2026-106337](https://patchblox.com/security/data/cve/CVE-2026-106337.md) | Routine | Chromium CVE-2026-106337: UI misrepresentation in UI | 5.4 | 0.0019 | | | [CVE-2026-106262](https://patchblox.com/security/data/cve/CVE-2026-106262.md) | Routine | Chromium CVE-2026-106262: Incomplete cleanup | 4.2 | 0.0019 | | | [CVE-2026-106216](https://patchblox.com/security/data/cve/CVE-2026-106216.md) | Routine | Chromium CVE-2026-106216: Cross-site request forgery | 5.4 | 0.0019 | | | [CVE-2026-106416](https://patchblox.com/security/data/cve/CVE-2026-106416.md) | Routine | Chromium CVE-2026-106416: Code injection | 5.4 | 0.0019 | | | [CVE-2026-106322](https://patchblox.com/security/data/cve/CVE-2026-106322.md) | Routine | Chromium CVE-2026-106322: Open redirect | 6.1 | 0.0018 | | | [CVE-2026-106251](https://patchblox.com/security/data/cve/CVE-2026-106251.md) | Routine | Chromium CVE-2026-106251: UI misrepresentation | 5.4 | 0.0018 | | | [CVE-2026-106272](https://patchblox.com/security/data/cve/CVE-2026-106272.md) | Routine | Chromium CVE-2026-106272: UI misrepresentation | 5.4 | 0.0018 | | | [CVE-2026-106316](https://patchblox.com/security/data/cve/CVE-2026-106316.md) | Routine | Chromium CVE-2026-106316: UI misrepresentation | 5.4 | 0.0018 | | | [CVE-2026-106400](https://patchblox.com/security/data/cve/CVE-2026-106400.md) | Routine | Chromium CVE-2026-106400: Clickjacking in Messages | 5.4 | 0.0018 | | | [CVE-2026-106420](https://patchblox.com/security/data/cve/CVE-2026-106420.md) | Routine | Chromium CVE-2026-106420: Incorrect calculation | 5.4 | 0.0018 | | | [CVE-2026-106339](https://patchblox.com/security/data/cve/CVE-2026-106339.md) | Routine | Chromium CVE-2026-106339: Use of released resource | 3.1 | 0.0018 | | | [CVE-2026-106244](https://patchblox.com/security/data/cve/CVE-2026-106244.md) | Routine | Chromium CVE-2026-106244: Incorrect authorization | 6.5 | 0.0018 | | | [CVE-2026-106344](https://patchblox.com/security/data/cve/CVE-2026-106344.md) | Routine | Chromium CVE-2026-106344: Missing authorization | 5.4 | 0.0018 | | | [CVE-2026-106324](https://patchblox.com/security/data/cve/CVE-2026-106324.md) | Routine | Chromium CVE-2026-106324: Incorrect authorization | 6.1 | 0.0018 | | | [CVE-2026-106288](https://patchblox.com/security/data/cve/CVE-2026-106288.md) | Routine | Chromium CVE-2026-106288: Missing authorization | 5.4 | 0.0018 | | | [CVE-2026-106253](https://patchblox.com/security/data/cve/CVE-2026-106253.md) | Routine | Chromium CVE-2026-106253: Incorrect authorization | 4.3 | 0.0018 | | | [CVE-2026-110143](https://patchblox.com/security/data/cve/CVE-2026-110143.md) | Routine | Chromium CVE-2026-110143: Use of uninitialized variable | 4.3 | 0.0018 | | | [CVE-2026-106320](https://patchblox.com/security/data/cve/CVE-2026-106320.md) | Routine | Chromium CVE-2026-106320: Use of released resource in UI | 4.2 | 0.0018 | | | [CVE-2026-106299](https://patchblox.com/security/data/cve/CVE-2026-106299.md) | Routine | Chromium CVE-2026-106299: Improper input validation | 5.4 | 0.0018 | | | [CVE-2026-106396](https://patchblox.com/security/data/cve/CVE-2026-106396.md) | Routine | Chromium CVE-2026-106396: Improper input validation | 5.4 | 0.0018 | | | [CVE-2026-106391](https://patchblox.com/security/data/cve/CVE-2026-106391.md) | Routine | Chromium CVE-2026-106391: Incorrect authorization | 4.2 | 0.0018 | | | [CVE-2026-110170](https://patchblox.com/security/data/cve/CVE-2026-110170.md) | Routine | Chromium CVE-2026-110170: Use after free | 4.3 | 0.0017 | | | [CVE-2026-110141](https://patchblox.com/security/data/cve/CVE-2026-110141.md) | Routine | Chromium CVE-2026-110141: Observable discrepancy | 3.1 | 0.0017 | | | [CVE-2026-106397](https://patchblox.com/security/data/cve/CVE-2026-106397.md) | Routine | Chromium CVE-2026-106397: Incorrect authorization in Mobile | 6.1 | 0.0017 | | | [CVE-2026-106250](https://patchblox.com/security/data/cve/CVE-2026-106250.md) | Routine | Chromium CVE-2026-106250: Missing authorization | 5.4 | 0.0017 | | | [CVE-2026-106259](https://patchblox.com/security/data/cve/CVE-2026-106259.md) | Routine | Chromium CVE-2026-106259: Incorrect authorization | 5.4 | 0.0017 | | | [CVE-2026-106296](https://patchblox.com/security/data/cve/CVE-2026-106296.md) | Routine | Chromium CVE-2026-106296: Improper privilege management in UI | 5.4 | 0.0017 | | | [CVE-2026-106427](https://patchblox.com/security/data/cve/CVE-2026-106427.md) | Routine | Chromium CVE-2026-106427: Confused deputy in Mobile | 5.4 | 0.0017 | | | [CVE-2026-106295](https://patchblox.com/security/data/cve/CVE-2026-106295.md) | Routine | Chromium CVE-2026-106295: Incorrect authorization | 4.2 | 0.0017 | | | [CVE-2026-106328](https://patchblox.com/security/data/cve/CVE-2026-106328.md) | Routine | Chromium CVE-2026-106328: Incorrect authorization | 5.9 | 0.0017 | | | [CVE-2026-106369](https://patchblox.com/security/data/cve/CVE-2026-106369.md) | Routine | Chromium CVE-2026-106369: Missing authorization | 4.2 | 0.0016 | | | [CVE-2026-106425](https://patchblox.com/security/data/cve/CVE-2026-106425.md) | Routine | Chromium CVE-2026-106425: Missing authorization | 4.2 | 0.0016 | | | [CVE-2026-106300](https://patchblox.com/security/data/cve/CVE-2026-106300.md) | Routine | Chromium CVE-2026-106300: Race condition | 4.7 | 0.0016 | | | [CVE-2026-106410](https://patchblox.com/security/data/cve/CVE-2026-106410.md) | Routine | Chromium CVE-2026-106410: Missing authorization | 4.2 | 0.0016 | | | [CVE-2026-106385](https://patchblox.com/security/data/cve/CVE-2026-106385.md) | Routine | Chromium CVE-2026-106385: Race condition | 5.3 | 0.0016 | | | [CVE-2026-110160](https://patchblox.com/security/data/cve/CVE-2026-110160.md) | Routine | Chromium CVE-2026-110160: Missing authorization | 4.2 | 0.0016 | | | [CVE-2026-106413](https://patchblox.com/security/data/cve/CVE-2026-106413.md) | Routine | Chromium CVE-2026-106413: Race condition | 4.2 | 0.0014 | | | [CVE-2026-106306](https://patchblox.com/security/data/cve/CVE-2026-106306.md) | Routine | Chromium CVE-2026-106306: Incorrect authorization | 5.4 | 0.0014 | | | [CVE-2026-106192](https://patchblox.com/security/data/cve/CVE-2026-106192.md) | Routine | Chromium CVE-2026-106192: Information leak in Mobile | 4.6 | 0.0014 | | | [CVE-2026-106243](https://patchblox.com/security/data/cve/CVE-2026-106243.md) | Routine | Chromium CVE-2026-106243: Incomplete cleanup | 5.3 | 0.0011 | | | [CVE-2026-106340](https://patchblox.com/security/data/cve/CVE-2026-106340.md) | Routine | Chromium CVE-2026-106340: Missing authorization | 4.6 | 0.0011 | | | [CVE-2026-110150](https://patchblox.com/security/data/cve/CVE-2026-110150.md) | Routine | Chromium CVE-2026-110150: Privilege elevation | 5.5 | 0.0009 | | | [CVE-2026-106313](https://patchblox.com/security/data/cve/CVE-2026-106313.md) | Routine | Chromium CVE-2026-106313: Incorrect authorization in Browser | 5.1 | 0.0009 | | | [CVE-2026-106254](https://patchblox.com/security/data/cve/CVE-2026-106254.md) | Routine | Chromium CVE-2026-106254: Information leak in Mobile | 5.1 | 0.0009 | | | [CVE-2026-106326](https://patchblox.com/security/data/cve/CVE-2026-106326.md) | Routine | Chromium CVE-2026-106326: Confused deputy in UI | 4.4 | 0.0008 | | | [CVE-2026-106405](https://patchblox.com/security/data/cve/CVE-2026-106405.md) | Routine | Chromium CVE-2026-106405: Race condition in CustomTabs | 6.0 | 0.0007 | | --- Data as of 2026-11-10T07:50:38Z 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.