# Microsoft Edge Dev 157.0.4322.0 Microsoft Edge Dev 157.0.4322.0, released October 6, 2026, fixes 361 CVEs in Microsoft Edge Dev. None of them is reported as exploited. Patch Radar priority: Urgent. The latest Microsoft Edge Dev is 159.0.4378.0, which also fixes every one of these CVEs. - Web page: https://patchblox.com/security/fix/windows-app/microsoft.edge.dev-157.0.4322.0 - Platform: Windows apps - Released: Oct 6, 2026 - Priority: Urgent (Closes CVE-2026-113303, rated Critical) - CVEs: 361, exploited: 0, on CISA KEV: 0 - Superseded by: [Microsoft Edge Dev 159.0.4378.0](https://patchblox.com/security/data/product/windows-app/microsoft-edge-dev.md), the latest version, which also fixes every CVE listed here ## Applies to | Product | Release | Fixed in | |---|---|---| | [Microsoft Edge Dev](https://patchblox.com/security/data/product/windows-app/microsoft-edge-dev.md) | | 157.0.4322.0 | ## CVEs this fix closes | CVE | Priority | Title | CVSS | EPSS | Exploitation | |---|---|---|---:|---:|---| | [CVE-2026-113303](https://patchblox.com/security/data/cve/CVE-2026-113303.md) | Urgent | Chromium CVE-2026-113303: Memory corruption | 8.8 | 0.0067 | | | [CVE-2026-113072](https://patchblox.com/security/data/cve/CVE-2026-113072.md) | Urgent | Chromium CVE-2026-113072: Memory corruption | 9.6 | 0.0056 | | | [CVE-2026-113271](https://patchblox.com/security/data/cve/CVE-2026-113271.md) | Urgent | Chromium CVE-2026-113271: Use after free | 8.8 | 0.0051 | | | [CVE-2026-113279](https://patchblox.com/security/data/cve/CVE-2026-113279.md) | Urgent | Chromium CVE-2026-113279: Memory corruption | 8.8 | 0.0051 | | | [CVE-2026-113280](https://patchblox.com/security/data/cve/CVE-2026-113280.md) | Urgent | Chromium CVE-2026-113280: Memory corruption | 8.8 | 0.0051 | | | [CVE-2026-118306](https://patchblox.com/security/data/cve/CVE-2026-118306.md) | Urgent | Chromium: CVE-2026-118306 Memory corruption in FileSystem | 9.6 | 0.0037 | | | [CVE-2026-118348](https://patchblox.com/security/data/cve/CVE-2026-118348.md) | Urgent | Chromium: CVE-2026-118348 Improper input validation in Skia | 9.6 | 0.0034 | | | [CVE-2026-118331](https://patchblox.com/security/data/cve/CVE-2026-118331.md) | Urgent | Chromium: CVE-2026-118331 Improper input validation in FileAPI | 8.8 | 0.0034 | | | [CVE-2026-118344](https://patchblox.com/security/data/cve/CVE-2026-118344.md) | Urgent | Chromium: CVE-2026-118344 Use after free in Layout | 8.8 | 0.0034 | | | [CVE-2026-76024](https://patchblox.com/security/data/cve/CVE-2026-76024.md) | Urgent | Chromium CVE-2026-76024: Memory corruption | 6.5 | 0.0026 | | | [CVE-2026-96196](https://patchblox.com/security/data/cve/CVE-2026-96196.md) | High | Microsoft Edge (Chromium-based) Security Feature Bypass Vulnerability | 8.8 | 0.0075 | | | [CVE-2026-113027](https://patchblox.com/security/data/cve/CVE-2026-113027.md) | High | Chromium CVE-2026-113027: Memory corruption | 8.8 | 0.0061 | | | [CVE-2026-113161](https://patchblox.com/security/data/cve/CVE-2026-113161.md) | High | Chromium CVE-2026-113161: Use after free | 8.8 | 0.0056 | | | [CVE-2026-113147](https://patchblox.com/security/data/cve/CVE-2026-113147.md) | High | Chromium CVE-2026-113147: Improper input validation | 8.8 | 0.0051 | | | [CVE-2026-113020](https://patchblox.com/security/data/cve/CVE-2026-113020.md) | High | Chromium CVE-2026-113020: Improper input validation | 9.6 | 0.0050 | | | [CVE-2026-113336](https://patchblox.com/security/data/cve/CVE-2026-113336.md) | High | Chromium CVE-2026-113336: Memory corruption | 9.6 | 0.0050 | | | [CVE-2026-113334](https://patchblox.com/security/data/cve/CVE-2026-113334.md) | High | Chromium CVE-2026-113334: Improper input validation | 8.8 | 0.0049 | | | [CVE-2026-113012](https://patchblox.com/security/data/cve/CVE-2026-113012.md) | High | Chromium CVE-2026-113012: Improper input validation | 8.8 | 0.0048 | | | [CVE-2026-113030](https://patchblox.com/security/data/cve/CVE-2026-113030.md) | High | Chromium CVE-2026-113030: Improper access control | 8.8 | 0.0048 | | | [CVE-2026-113192](https://patchblox.com/security/data/cve/CVE-2026-113192.md) | High | Chromium CVE-2026-113192: Memory corruption | 8.8 | 0.0048 | | | [CVE-2026-113037](https://patchblox.com/security/data/cve/CVE-2026-113037.md) | High | Chromium CVE-2026-113037: Use after free | 8.8 | 0.0047 | | | [CVE-2026-113273](https://patchblox.com/security/data/cve/CVE-2026-113273.md) | High | Chromium CVE-2026-113273: Memory corruption | 8.8 | 0.0047 | | | [CVE-2026-113034](https://patchblox.com/security/data/cve/CVE-2026-113034.md) | High | Chromium CVE-2026-113034: Memory corruption | 8.8 | 0.0046 | | | [CVE-2026-113168](https://patchblox.com/security/data/cve/CVE-2026-113168.md) | High | Chromium CVE-2026-113168: Use after free | 8.8 | 0.0046 | | | [CVE-2026-113044](https://patchblox.com/security/data/cve/CVE-2026-113044.md) | High | Chromium CVE-2026-113044: Use after free | 8.8 | 0.0046 | | | [CVE-2026-113017](https://patchblox.com/security/data/cve/CVE-2026-113017.md) | High | Chromium CVE-2026-113017: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113019](https://patchblox.com/security/data/cve/CVE-2026-113019.md) | High | Chromium CVE-2026-113019: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113160](https://patchblox.com/security/data/cve/CVE-2026-113160.md) | High | Chromium CVE-2026-113160: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113162](https://patchblox.com/security/data/cve/CVE-2026-113162.md) | High | Chromium CVE-2026-113162: Improper input validation | 8.8 | 0.0044 | | | [CVE-2026-113181](https://patchblox.com/security/data/cve/CVE-2026-113181.md) | High | Chromium CVE-2026-113181: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113248](https://patchblox.com/security/data/cve/CVE-2026-113248.md) | High | Chromium CVE-2026-113248: Memory corruption | 8.8 | 0.0044 | | | [CVE-2026-113293](https://patchblox.com/security/data/cve/CVE-2026-113293.md) | High | Chromium CVE-2026-113293: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113305](https://patchblox.com/security/data/cve/CVE-2026-113305.md) | High | Chromium CVE-2026-113305: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113316](https://patchblox.com/security/data/cve/CVE-2026-113316.md) | High | Chromium CVE-2026-113316: Improper input validation | 8.8 | 0.0044 | | | [CVE-2026-113318](https://patchblox.com/security/data/cve/CVE-2026-113318.md) | High | Chromium CVE-2026-113318: Memory corruption | 8.8 | 0.0044 | | | [CVE-2026-113337](https://patchblox.com/security/data/cve/CVE-2026-113337.md) | High | Chromium CVE-2026-113337: Memory corruption | 8.8 | 0.0044 | | | [CVE-2026-113338](https://patchblox.com/security/data/cve/CVE-2026-113338.md) | High | Chromium CVE-2026-113338: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113339](https://patchblox.com/security/data/cve/CVE-2026-113339.md) | High | Chromium CVE-2026-113339: Use after free | 8.8 | 0.0044 | | | [CVE-2026-113101](https://patchblox.com/security/data/cve/CVE-2026-113101.md) | High | Chromium CVE-2026-113101: Use after free | 8.8 | 0.0043 | | | [CVE-2026-113108](https://patchblox.com/security/data/cve/CVE-2026-113108.md) | High | Chromium CVE-2026-113108: Use after free | 8.8 | 0.0043 | | | [CVE-2026-113240](https://patchblox.com/security/data/cve/CVE-2026-113240.md) | High | Chromium CVE-2026-113240: Use after free | 8.8 | 0.0043 | | | [CVE-2026-113250](https://patchblox.com/security/data/cve/CVE-2026-113250.md) | High | Chromium CVE-2026-113250: Use after free | 8.8 | 0.0043 | | | [CVE-2026-113319](https://patchblox.com/security/data/cve/CVE-2026-113319.md) | High | Chromium CVE-2026-113319: Use after free | 8.8 | 0.0043 | | | [CVE-2026-113257](https://patchblox.com/security/data/cve/CVE-2026-113257.md) | High | Chromium CVE-2026-113257: Memory corruption | 8.8 | 0.0043 | | | [CVE-2026-113284](https://patchblox.com/security/data/cve/CVE-2026-113284.md) | High | Chromium CVE-2026-113284: Memory corruption | 8.8 | 0.0043 | | | [CVE-2026-112998](https://patchblox.com/security/data/cve/CVE-2026-112998.md) | High | Chromium CVE-2026-112998: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113003](https://patchblox.com/security/data/cve/CVE-2026-113003.md) | High | Chromium CVE-2026-113003: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113093](https://patchblox.com/security/data/cve/CVE-2026-113093.md) | High | Chromium CVE-2026-113093: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113095](https://patchblox.com/security/data/cve/CVE-2026-113095.md) | High | Chromium CVE-2026-113095: Out of bounds read | 8.8 | 0.0042 | | | [CVE-2026-113104](https://patchblox.com/security/data/cve/CVE-2026-113104.md) | High | Chromium CVE-2026-113104: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113133](https://patchblox.com/security/data/cve/CVE-2026-113133.md) | High | Chromium CVE-2026-113133: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113154](https://patchblox.com/security/data/cve/CVE-2026-113154.md) | High | Chromium CVE-2026-113154: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113232](https://patchblox.com/security/data/cve/CVE-2026-113232.md) | High | Chromium CVE-2026-113232: Memory corruption | 8.8 | 0.0042 | | | [CVE-2026-113212](https://patchblox.com/security/data/cve/CVE-2026-113212.md) | High | Chromium CVE-2026-113212: Memory corruption | 8.3 | 0.0041 | | | [CVE-2026-113343](https://patchblox.com/security/data/cve/CVE-2026-113343.md) | High | Chromium CVE-2026-113343: Memory corruption | 8.8 | 0.0041 | | | [CVE-2026-113033](https://patchblox.com/security/data/cve/CVE-2026-113033.md) | High | Chromium CVE-2026-113033: Use after free | 8.8 | 0.0041 | | | [CVE-2026-113029](https://patchblox.com/security/data/cve/CVE-2026-113029.md) | High | Chromium CVE-2026-113029: Improper access control | 8.8 | 0.0040 | | | [CVE-2026-113175](https://patchblox.com/security/data/cve/CVE-2026-113175.md) | High | Chromium CVE-2026-113175: Improper input validation | 8.8 | 0.0040 | | | [CVE-2026-113252](https://patchblox.com/security/data/cve/CVE-2026-113252.md) | High | Chromium CVE-2026-113252: Improper input validation | 9.6 | 0.0040 | | | [CVE-2026-113210](https://patchblox.com/security/data/cve/CVE-2026-113210.md) | High | Chromium CVE-2026-113210: Use after free | 8.8 | 0.0040 | | | [CVE-2026-113242](https://patchblox.com/security/data/cve/CVE-2026-113242.md) | High | Chromium CVE-2026-113242: Memory corruption | 8.8 | 0.0040 | | | [CVE-2026-113315](https://patchblox.com/security/data/cve/CVE-2026-113315.md) | High | Chromium CVE-2026-113315: Memory corruption | 8.8 | 0.0040 | | | [CVE-2026-113324](https://patchblox.com/security/data/cve/CVE-2026-113324.md) | High | Chromium CVE-2026-113324: Use after free | 8.8 | 0.0040 | | | [CVE-2026-113332](https://patchblox.com/security/data/cve/CVE-2026-113332.md) | High | Chromium CVE-2026-113332: Memory corruption | 8.8 | 0.0040 | | | [CVE-2026-118305](https://patchblox.com/security/data/cve/CVE-2026-118305.md) | High | Chromium: CVE-2026-118305 Memory corruption in Turbolev | 9.6 | 0.0040 | | | [CVE-2026-113039](https://patchblox.com/security/data/cve/CVE-2026-113039.md) | High | Chromium CVE-2026-113039: Use after free | 8.8 | 0.0039 | | | [CVE-2026-113258](https://patchblox.com/security/data/cve/CVE-2026-113258.md) | High | Chromium CVE-2026-113258: Memory corruption | 8.8 | 0.0039 | | | [CVE-2026-113213](https://patchblox.com/security/data/cve/CVE-2026-113213.md) | High | Chromium CVE-2026-113213: Memory corruption | 8.8 | 0.0039 | | | [CVE-2026-113140](https://patchblox.com/security/data/cve/CVE-2026-113140.md) | High | Chromium CVE-2026-113140: Use after free | 8.8 | 0.0039 | | | [CVE-2026-113188](https://patchblox.com/security/data/cve/CVE-2026-113188.md) | High | Chromium CVE-2026-113188: Memory corruption | 8.8 | 0.0039 | | | [CVE-2026-113267](https://patchblox.com/security/data/cve/CVE-2026-113267.md) | High | Chromium CVE-2026-113267: Memory corruption | 8.8 | 0.0039 | | | [CVE-2026-113285](https://patchblox.com/security/data/cve/CVE-2026-113285.md) | High | Chromium CVE-2026-113285: Memory corruption | 8.8 | 0.0039 | | | [CVE-2026-113313](https://patchblox.com/security/data/cve/CVE-2026-113313.md) | High | Chromium CVE-2026-113313: Memory corruption | 8.8 | 0.0039 | | | [CVE-2026-113040](https://patchblox.com/security/data/cve/CVE-2026-113040.md) | High | Chromium CVE-2026-113040: Improper input validation | 8.8 | 0.0039 | | | [CVE-2026-113065](https://patchblox.com/security/data/cve/CVE-2026-113065.md) | High | Chromium CVE-2026-113065: Use after free | 8.8 | 0.0039 | | | [CVE-2026-113021](https://patchblox.com/security/data/cve/CVE-2026-113021.md) | High | Chromium CVE-2026-113021: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113274](https://patchblox.com/security/data/cve/CVE-2026-113274.md) | High | Chromium CVE-2026-113274: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113106](https://patchblox.com/security/data/cve/CVE-2026-113106.md) | High | Chromium CVE-2026-113106: Memory corruption | 9.6 | 0.0038 | | | [CVE-2026-113015](https://patchblox.com/security/data/cve/CVE-2026-113015.md) | High | Chromium CVE-2026-113015: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113024](https://patchblox.com/security/data/cve/CVE-2026-113024.md) | High | Chromium CVE-2026-113024: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113031](https://patchblox.com/security/data/cve/CVE-2026-113031.md) | High | Chromium CVE-2026-113031: Memory corruption | 8.8 | 0.0038 | | | [CVE-2026-113073](https://patchblox.com/security/data/cve/CVE-2026-113073.md) | High | Chromium CVE-2026-113073: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113081](https://patchblox.com/security/data/cve/CVE-2026-113081.md) | High | Chromium CVE-2026-113081: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113087](https://patchblox.com/security/data/cve/CVE-2026-113087.md) | High | Chromium CVE-2026-113087: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113120](https://patchblox.com/security/data/cve/CVE-2026-113120.md) | High | Chromium CVE-2026-113120: Improper input validation | 8.8 | 0.0038 | | | [CVE-2026-113123](https://patchblox.com/security/data/cve/CVE-2026-113123.md) | High | Chromium CVE-2026-113123: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113174](https://patchblox.com/security/data/cve/CVE-2026-113174.md) | High | Chromium CVE-2026-113174: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113183](https://patchblox.com/security/data/cve/CVE-2026-113183.md) | High | Chromium CVE-2026-113183: Memory corruption | 8.8 | 0.0038 | | | [CVE-2026-113202](https://patchblox.com/security/data/cve/CVE-2026-113202.md) | High | Chromium CVE-2026-113202: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113215](https://patchblox.com/security/data/cve/CVE-2026-113215.md) | High | Chromium CVE-2026-113215: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113234](https://patchblox.com/security/data/cve/CVE-2026-113234.md) | High | Chromium CVE-2026-113234: Memory corruption | 8.8 | 0.0038 | | | [CVE-2026-113294](https://patchblox.com/security/data/cve/CVE-2026-113294.md) | High | Chromium CVE-2026-113294: Improper input validation | 8.8 | 0.0038 | | | [CVE-2026-113299](https://patchblox.com/security/data/cve/CVE-2026-113299.md) | High | Chromium CVE-2026-113299: Memory corruption | 8.8 | 0.0038 | | | [CVE-2026-113301](https://patchblox.com/security/data/cve/CVE-2026-113301.md) | High | Chromium CVE-2026-113301: Memory corruption | 8.8 | 0.0038 | | | [CVE-2026-113272](https://patchblox.com/security/data/cve/CVE-2026-113272.md) | High | Chromium CVE-2026-113272: Memory corruption | 8.8 | 0.0038 | | | [CVE-2026-113314](https://patchblox.com/security/data/cve/CVE-2026-113314.md) | High | Chromium CVE-2026-113314: Use after free | 8.8 | 0.0038 | | | [CVE-2026-113328](https://patchblox.com/security/data/cve/CVE-2026-113328.md) | High | Chromium CVE-2026-113328: Improper input validation | 9.6 | 0.0037 | | | [CVE-2026-113195](https://patchblox.com/security/data/cve/CVE-2026-113195.md) | High | Chromium CVE-2026-113195: Improper input validation | 8.8 | 0.0037 | | | [CVE-2026-113243](https://patchblox.com/security/data/cve/CVE-2026-113243.md) | High | Chromium CVE-2026-113243: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113269](https://patchblox.com/security/data/cve/CVE-2026-113269.md) | High | Chromium CVE-2026-113269: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113300](https://patchblox.com/security/data/cve/CVE-2026-113300.md) | High | Chromium CVE-2026-113300: Out of bounds write | 9.6 | 0.0037 | | | [CVE-2026-113025](https://patchblox.com/security/data/cve/CVE-2026-113025.md) | High | Chromium CVE-2026-113025: Use after free | 8.8 | 0.0037 | | | [CVE-2026-113086](https://patchblox.com/security/data/cve/CVE-2026-113086.md) | High | Chromium CVE-2026-113086: Improper input validation | 8.8 | 0.0037 | | | [CVE-2026-113135](https://patchblox.com/security/data/cve/CVE-2026-113135.md) | High | Chromium CVE-2026-113135: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113143](https://patchblox.com/security/data/cve/CVE-2026-113143.md) | High | Chromium CVE-2026-113143: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113167](https://patchblox.com/security/data/cve/CVE-2026-113167.md) | High | Chromium CVE-2026-113167: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113182](https://patchblox.com/security/data/cve/CVE-2026-113182.md) | High | Chromium CVE-2026-113182: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113194](https://patchblox.com/security/data/cve/CVE-2026-113194.md) | High | Chromium CVE-2026-113194: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113197](https://patchblox.com/security/data/cve/CVE-2026-113197.md) | High | Chromium CVE-2026-113197: Use after free | 8.8 | 0.0037 | | | [CVE-2026-113206](https://patchblox.com/security/data/cve/CVE-2026-113206.md) | High | Chromium CVE-2026-113206: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113298](https://patchblox.com/security/data/cve/CVE-2026-113298.md) | High | Chromium CVE-2026-113298: Use after free | 8.8 | 0.0037 | | | [CVE-2026-113308](https://patchblox.com/security/data/cve/CVE-2026-113308.md) | High | Chromium CVE-2026-113308: Use after free | 8.8 | 0.0037 | | | [CVE-2026-113331](https://patchblox.com/security/data/cve/CVE-2026-113331.md) | High | Chromium CVE-2026-113331: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113200](https://patchblox.com/security/data/cve/CVE-2026-113200.md) | High | Chromium CVE-2026-113200: Use after free | 8.8 | 0.0037 | | | [CVE-2026-113130](https://patchblox.com/security/data/cve/CVE-2026-113130.md) | High | Chromium CVE-2026-113130: Use after free | 8.8 | 0.0037 | | | [CVE-2026-113132](https://patchblox.com/security/data/cve/CVE-2026-113132.md) | High | Chromium CVE-2026-113132: Memory corruption | 8.8 | 0.0037 | | | [CVE-2026-113281](https://patchblox.com/security/data/cve/CVE-2026-113281.md) | High | Chromium CVE-2026-113281: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113018](https://patchblox.com/security/data/cve/CVE-2026-113018.md) | High | Chromium CVE-2026-113018: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113214](https://patchblox.com/security/data/cve/CVE-2026-113214.md) | High | Chromium CVE-2026-113214: Improper input validation | 8.8 | 0.0036 | | | [CVE-2026-113261](https://patchblox.com/security/data/cve/CVE-2026-113261.md) | High | Chromium CVE-2026-113261: Use after free | 9.6 | 0.0036 | | | [CVE-2026-113342](https://patchblox.com/security/data/cve/CVE-2026-113342.md) | High | Chromium CVE-2026-113342: Memory corruption | 9.6 | 0.0036 | | | [CVE-2026-118358](https://patchblox.com/security/data/cve/CVE-2026-118358.md) | High | Chromium: CVE-2026-118358 Memory corruption in WebAudio | 8.8 | 0.0036 | | | [CVE-2026-113222](https://patchblox.com/security/data/cve/CVE-2026-113222.md) | High | Chromium CVE-2026-113222: Use after free | 9.6 | 0.0036 | | | [CVE-2026-112993](https://patchblox.com/security/data/cve/CVE-2026-112993.md) | High | Chromium CVE-2026-112993: Use after free | 8.8 | 0.0036 | | | [CVE-2026-112996](https://patchblox.com/security/data/cve/CVE-2026-112996.md) | High | Chromium CVE-2026-112996: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113001](https://patchblox.com/security/data/cve/CVE-2026-113001.md) | High | Chromium CVE-2026-113001: Use after free | 8.8 | 0.0036 | | | [CVE-2026-113058](https://patchblox.com/security/data/cve/CVE-2026-113058.md) | High | Chromium CVE-2026-113058: Use after free | 8.8 | 0.0036 | | | [CVE-2026-113110](https://patchblox.com/security/data/cve/CVE-2026-113110.md) | High | Chromium CVE-2026-113110: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113127](https://patchblox.com/security/data/cve/CVE-2026-113127.md) | High | Chromium CVE-2026-113127: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113014](https://patchblox.com/security/data/cve/CVE-2026-113014.md) | High | Chromium CVE-2026-113014: Use after free | 9.6 | 0.0036 | | | [CVE-2026-113235](https://patchblox.com/security/data/cve/CVE-2026-113235.md) | High | Chromium CVE-2026-113235: Improper input validation | 9.6 | 0.0036 | | | [CVE-2026-113172](https://patchblox.com/security/data/cve/CVE-2026-113172.md) | High | Chromium CVE-2026-113172: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113179](https://patchblox.com/security/data/cve/CVE-2026-113179.md) | High | Chromium CVE-2026-113179: Use after free | 8.8 | 0.0036 | | | [CVE-2026-113184](https://patchblox.com/security/data/cve/CVE-2026-113184.md) | High | Chromium CVE-2026-113184: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113198](https://patchblox.com/security/data/cve/CVE-2026-113198.md) | High | Chromium CVE-2026-113198: Use after free | 8.8 | 0.0036 | | | [CVE-2026-113244](https://patchblox.com/security/data/cve/CVE-2026-113244.md) | High | Chromium CVE-2026-113244: Improper input validation | 8.8 | 0.0036 | | | [CVE-2026-113327](https://patchblox.com/security/data/cve/CVE-2026-113327.md) | High | Chromium CVE-2026-113327: Use after free | 8.8 | 0.0036 | | | [CVE-2026-113189](https://patchblox.com/security/data/cve/CVE-2026-113189.md) | High | Chromium CVE-2026-113189: Use after free | 9.6 | 0.0036 | | | [CVE-2026-113260](https://patchblox.com/security/data/cve/CVE-2026-113260.md) | High | Chromium CVE-2026-113260: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113288](https://patchblox.com/security/data/cve/CVE-2026-113288.md) | High | Chromium CVE-2026-113288: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113291](https://patchblox.com/security/data/cve/CVE-2026-113291.md) | High | Chromium CVE-2026-113291: Memory corruption | 8.8 | 0.0036 | | | [CVE-2026-113007](https://patchblox.com/security/data/cve/CVE-2026-113007.md) | High | Chromium CVE-2026-113007: Memory corruption | 9.6 | 0.0035 | | | [CVE-2026-113126](https://patchblox.com/security/data/cve/CVE-2026-113126.md) | High | Chromium CVE-2026-113126: Memory corruption | 9.6 | 0.0035 | | | [CVE-2026-113094](https://patchblox.com/security/data/cve/CVE-2026-113094.md) | High | Chromium CVE-2026-113094: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113111](https://patchblox.com/security/data/cve/CVE-2026-113111.md) | High | Chromium CVE-2026-113111: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113306](https://patchblox.com/security/data/cve/CVE-2026-113306.md) | High | Chromium CVE-2026-113306: Improper input validation | 8.8 | 0.0035 | | | [CVE-2026-113245](https://patchblox.com/security/data/cve/CVE-2026-113245.md) | High | Chromium CVE-2026-113245: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113254](https://patchblox.com/security/data/cve/CVE-2026-113254.md) | High | Chromium CVE-2026-113254: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-112992](https://patchblox.com/security/data/cve/CVE-2026-112992.md) | High | Chromium CVE-2026-112992: Memory corruption | 9.6 | 0.0035 | | | [CVE-2026-113056](https://patchblox.com/security/data/cve/CVE-2026-113056.md) | High | Chromium CVE-2026-113056: Memory corruption | 9.6 | 0.0035 | | | [CVE-2026-113138](https://patchblox.com/security/data/cve/CVE-2026-113138.md) | High | Chromium CVE-2026-113138: Memory corruption | 9.6 | 0.0035 | | | [CVE-2026-112997](https://patchblox.com/security/data/cve/CVE-2026-112997.md) | High | Chromium CVE-2026-112997: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113000](https://patchblox.com/security/data/cve/CVE-2026-113000.md) | High | Chromium CVE-2026-113000: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113049](https://patchblox.com/security/data/cve/CVE-2026-113049.md) | High | Chromium CVE-2026-113049: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113068](https://patchblox.com/security/data/cve/CVE-2026-113068.md) | High | Chromium CVE-2026-113068: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113079](https://patchblox.com/security/data/cve/CVE-2026-113079.md) | High | Chromium CVE-2026-113079: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113124](https://patchblox.com/security/data/cve/CVE-2026-113124.md) | High | Chromium CVE-2026-113124: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113134](https://patchblox.com/security/data/cve/CVE-2026-113134.md) | High | Chromium CVE-2026-113134: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113149](https://patchblox.com/security/data/cve/CVE-2026-113149.md) | High | Chromium CVE-2026-113149: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113226](https://patchblox.com/security/data/cve/CVE-2026-113226.md) | High | Chromium CVE-2026-113226: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113230](https://patchblox.com/security/data/cve/CVE-2026-113230.md) | High | Chromium CVE-2026-113230: Improper input validation | 8.8 | 0.0035 | | | [CVE-2026-113216](https://patchblox.com/security/data/cve/CVE-2026-113216.md) | High | Chromium CVE-2026-113216: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113270](https://patchblox.com/security/data/cve/CVE-2026-113270.md) | High | Chromium CVE-2026-113270: Use after free | 9.6 | 0.0035 | | | [CVE-2026-113227](https://patchblox.com/security/data/cve/CVE-2026-113227.md) | High | Chromium CVE-2026-113227: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113256](https://patchblox.com/security/data/cve/CVE-2026-113256.md) | High | Chromium CVE-2026-113256: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113265](https://patchblox.com/security/data/cve/CVE-2026-113265.md) | High | Chromium CVE-2026-113265: Memory corruption | 8.8 | 0.0035 | | | [CVE-2026-113287](https://patchblox.com/security/data/cve/CVE-2026-113287.md) | High | Chromium CVE-2026-113287: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113290](https://patchblox.com/security/data/cve/CVE-2026-113290.md) | High | Chromium CVE-2026-113290: Use after free | 8.8 | 0.0035 | | | [CVE-2026-113074](https://patchblox.com/security/data/cve/CVE-2026-113074.md) | High | Chromium CVE-2026-113074: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113187](https://patchblox.com/security/data/cve/CVE-2026-113187.md) | High | Chromium CVE-2026-113187: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113286](https://patchblox.com/security/data/cve/CVE-2026-113286.md) | High | Chromium CVE-2026-113286: Memory corruption | 8.8 | 0.0034 | | | [CVE-2026-113289](https://patchblox.com/security/data/cve/CVE-2026-113289.md) | High | Chromium CVE-2026-113289: Improper input validation | 8.8 | 0.0034 | | | [CVE-2026-113307](https://patchblox.com/security/data/cve/CVE-2026-113307.md) | High | Chromium CVE-2026-113307: Memory corruption | 8.8 | 0.0034 | | | [CVE-2026-113251](https://patchblox.com/security/data/cve/CVE-2026-113251.md) | High | Chromium CVE-2026-113251: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113078](https://patchblox.com/security/data/cve/CVE-2026-113078.md) | High | Chromium CVE-2026-113078: Improper input validation | 9.6 | 0.0034 | | | [CVE-2026-113005](https://patchblox.com/security/data/cve/CVE-2026-113005.md) | High | Chromium CVE-2026-113005: Memory corruption | 8.8 | 0.0034 | | | [CVE-2026-113006](https://patchblox.com/security/data/cve/CVE-2026-113006.md) | High | Chromium CVE-2026-113006: Out of bounds read | 8.8 | 0.0034 | | | [CVE-2026-113097](https://patchblox.com/security/data/cve/CVE-2026-113097.md) | High | Chromium CVE-2026-113097: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113105](https://patchblox.com/security/data/cve/CVE-2026-113105.md) | High | Chromium CVE-2026-113105: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113114](https://patchblox.com/security/data/cve/CVE-2026-113114.md) | High | Chromium CVE-2026-113114: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113153](https://patchblox.com/security/data/cve/CVE-2026-113153.md) | High | Chromium CVE-2026-113153: Memory corruption | 8.8 | 0.0034 | | | [CVE-2026-113155](https://patchblox.com/security/data/cve/CVE-2026-113155.md) | High | Chromium CVE-2026-113155: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113152](https://patchblox.com/security/data/cve/CVE-2026-113152.md) | High | Chromium CVE-2026-113152: Memory corruption | 8.8 | 0.0034 | | | [CVE-2026-113203](https://patchblox.com/security/data/cve/CVE-2026-113203.md) | High | Chromium CVE-2026-113203: Use after free | 8.8 | 0.0034 | | | [CVE-2026-113131](https://patchblox.com/security/data/cve/CVE-2026-113131.md) | High | Chromium CVE-2026-113131: Memory corruption | 8.8 | 0.0034 | | | [CVE-2026-112994](https://patchblox.com/security/data/cve/CVE-2026-112994.md) | High | Chromium CVE-2026-112994: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-112995](https://patchblox.com/security/data/cve/CVE-2026-112995.md) | High | Chromium CVE-2026-112995: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113009](https://patchblox.com/security/data/cve/CVE-2026-113009.md) | High | Chromium CVE-2026-113009: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113128](https://patchblox.com/security/data/cve/CVE-2026-113128.md) | High | Chromium CVE-2026-113128: Missing authorization | 8.8 | 0.0033 | | | [CVE-2026-118330](https://patchblox.com/security/data/cve/CVE-2026-118330.md) | High | Chromium: CVE-2026-118330 Use after free in Browser | 8.8 | 0.0033 | | | [CVE-2026-113052](https://patchblox.com/security/data/cve/CVE-2026-113052.md) | High | Chromium CVE-2026-113052: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113190](https://patchblox.com/security/data/cve/CVE-2026-113190.md) | High | Chromium CVE-2026-113190: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113023](https://patchblox.com/security/data/cve/CVE-2026-113023.md) | High | Chromium CVE-2026-113023: Improper input validation | 9.6 | 0.0033 | | | [CVE-2026-113061](https://patchblox.com/security/data/cve/CVE-2026-113061.md) | High | Chromium CVE-2026-113061: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113022](https://patchblox.com/security/data/cve/CVE-2026-113022.md) | High | Chromium CVE-2026-113022: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113113](https://patchblox.com/security/data/cve/CVE-2026-113113.md) | High | Chromium CVE-2026-113113: Use after free | 8.8 | 0.0033 | | | [CVE-2026-118307](https://patchblox.com/security/data/cve/CVE-2026-118307.md) | High | Chromium: CVE-2026-118307 Use after free in Paint | 8.8 | 0.0033 | | | [CVE-2026-113089](https://patchblox.com/security/data/cve/CVE-2026-113089.md) | High | Chromium CVE-2026-113089: Improper input validation | 9.6 | 0.0033 | | | [CVE-2026-113013](https://patchblox.com/security/data/cve/CVE-2026-113013.md) | High | Chromium CVE-2026-113013: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113185](https://patchblox.com/security/data/cve/CVE-2026-113185.md) | High | Chromium CVE-2026-113185: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113247](https://patchblox.com/security/data/cve/CVE-2026-113247.md) | High | Chromium CVE-2026-113247: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113302](https://patchblox.com/security/data/cve/CVE-2026-113302.md) | High | Chromium CVE-2026-113302: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113321](https://patchblox.com/security/data/cve/CVE-2026-113321.md) | High | Chromium CVE-2026-113321: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113211](https://patchblox.com/security/data/cve/CVE-2026-113211.md) | High | Chromium CVE-2026-113211: Memory corruption | 9.6 | 0.0033 | | | [CVE-2026-113080](https://patchblox.com/security/data/cve/CVE-2026-113080.md) | High | Chromium CVE-2026-113080: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113278](https://patchblox.com/security/data/cve/CVE-2026-113278.md) | High | Chromium CVE-2026-113278: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113283](https://patchblox.com/security/data/cve/CVE-2026-113283.md) | High | Chromium CVE-2026-113283: Memory corruption | 9.6 | 0.0033 | | | [CVE-2026-113219](https://patchblox.com/security/data/cve/CVE-2026-113219.md) | High | Chromium CVE-2026-113219: Memory corruption | 8.8 | 0.0033 | | | [CVE-2026-113158](https://patchblox.com/security/data/cve/CVE-2026-113158.md) | High | Chromium CVE-2026-113158: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113177](https://patchblox.com/security/data/cve/CVE-2026-113177.md) | High | Chromium CVE-2026-113177: Use after free | 8.8 | 0.0033 | | | [CVE-2026-113264](https://patchblox.com/security/data/cve/CVE-2026-113264.md) | High | Chromium CVE-2026-113264: Improper input validation | 8.8 | 0.0033 | | | [CVE-2026-113036](https://patchblox.com/security/data/cve/CVE-2026-113036.md) | High | Chromium CVE-2026-113036: Memory corruption | 8.8 | 0.0032 | | | [CVE-2026-113146](https://patchblox.com/security/data/cve/CVE-2026-113146.md) | High | Chromium CVE-2026-113146: Memory corruption | 8.8 | 0.0032 | | | [CVE-2026-113004](https://patchblox.com/security/data/cve/CVE-2026-113004.md) | High | Chromium CVE-2026-113004: Memory corruption | 8.8 | 0.0032 | | | [CVE-2026-113067](https://patchblox.com/security/data/cve/CVE-2026-113067.md) | High | Chromium CVE-2026-113067: Use after free | 8.8 | 0.0032 | | | [CVE-2026-113100](https://patchblox.com/security/data/cve/CVE-2026-113100.md) | High | Chromium CVE-2026-113100: Memory corruption | 8.8 | 0.0032 | | | [CVE-2026-113275](https://patchblox.com/security/data/cve/CVE-2026-113275.md) | High | Chromium CVE-2026-113275: Use after free | 8.8 | 0.0032 | | | [CVE-2026-113062](https://patchblox.com/security/data/cve/CVE-2026-113062.md) | High | Chromium CVE-2026-113062: Improper input validation | 8.8 | 0.0032 | | | [CVE-2026-118317](https://patchblox.com/security/data/cve/CVE-2026-118317.md) | High | Chromium: CVE-2026-118317 Memory corruption in HTML | 8.8 | 0.0032 | | | [CVE-2026-118339](https://patchblox.com/security/data/cve/CVE-2026-118339.md) | High | Chromium: CVE-2026-118339 Use after free in Animation | 8.8 | 0.0032 | | | [CVE-2026-119261](https://patchblox.com/security/data/cve/CVE-2026-119261.md) | High | Chromium CVE-2026-119261: Improper input validation | 9.6 | 0.0032 | | | [CVE-2026-113063](https://patchblox.com/security/data/cve/CVE-2026-113063.md) | High | Chromium CVE-2026-113063: Improper input validation | 8.8 | 0.0032 | | | [CVE-2026-113262](https://patchblox.com/security/data/cve/CVE-2026-113262.md) | High | Chromium CVE-2026-113262: Use after free | 8.8 | 0.0032 | | | [CVE-2026-113085](https://patchblox.com/security/data/cve/CVE-2026-113085.md) | High | Chromium CVE-2026-113085: Use after free | 8.8 | 0.0032 | | | [CVE-2026-113148](https://patchblox.com/security/data/cve/CVE-2026-113148.md) | High | Chromium CVE-2026-113148: Memory corruption | 8.8 | 0.0031 | | | [CVE-2026-113259](https://patchblox.com/security/data/cve/CVE-2026-113259.md) | High | Chromium CVE-2026-113259: Use after free | 8.8 | 0.0031 | | | [CVE-2026-113028](https://patchblox.com/security/data/cve/CVE-2026-113028.md) | High | Chromium CVE-2026-113028: Use after free | 8.8 | 0.0031 | | | [CVE-2026-113042](https://patchblox.com/security/data/cve/CVE-2026-113042.md) | High | Chromium CVE-2026-113042: Use after free | 8.8 | 0.0031 | | | [CVE-2026-113109](https://patchblox.com/security/data/cve/CVE-2026-113109.md) | High | Chromium CVE-2026-113109: Memory corruption | 8.8 | 0.0031 | | | [CVE-2026-113208](https://patchblox.com/security/data/cve/CVE-2026-113208.md) | High | Chromium CVE-2026-113208: Use after free | 8.8 | 0.0031 | | | [CVE-2026-113253](https://patchblox.com/security/data/cve/CVE-2026-113253.md) | High | Chromium CVE-2026-113253: Use after free | 8.8 | 0.0031 | | | [CVE-2026-113176](https://patchblox.com/security/data/cve/CVE-2026-113176.md) | High | Chromium CVE-2026-113176: Memory corruption | 8.8 | 0.0031 | | | [CVE-2026-113125](https://patchblox.com/security/data/cve/CVE-2026-113125.md) | High | Chromium CVE-2026-113125: Memory corruption | 8.8 | 0.0031 | | | [CVE-2026-113084](https://patchblox.com/security/data/cve/CVE-2026-113084.md) | High | Chromium CVE-2026-113084: Improper input validation | 9.6 | 0.0031 | | | [CVE-2026-113046](https://patchblox.com/security/data/cve/CVE-2026-113046.md) | High | Chromium CVE-2026-113046: Improper input validation | 8.8 | 0.0031 | | | [CVE-2026-113090](https://patchblox.com/security/data/cve/CVE-2026-113090.md) | High | Chromium CVE-2026-113090: Memory corruption | 8.8 | 0.0031 | | | [CVE-2026-113221](https://patchblox.com/security/data/cve/CVE-2026-113221.md) | High | Chromium CVE-2026-113221: Use after free | 8.8 | 0.0031 | | | [CVE-2026-118308](https://patchblox.com/security/data/cve/CVE-2026-118308.md) | High | Chromium: CVE-2026-118308 Use after free in SVG | 9.6 | 0.0031 | | | [CVE-2026-118310](https://patchblox.com/security/data/cve/CVE-2026-118310.md) | High | Chromium: CVE-2026-118310 Improper input validation in Views | 9.6 | 0.0031 | | | [CVE-2026-113011](https://patchblox.com/security/data/cve/CVE-2026-113011.md) | High | Chromium CVE-2026-113011: Use after free | 8.8 | 0.0030 | | | [CVE-2026-112999](https://patchblox.com/security/data/cve/CVE-2026-112999.md) | High | Chromium CVE-2026-112999: Use after free | 8.8 | 0.0030 | | | [CVE-2026-113069](https://patchblox.com/security/data/cve/CVE-2026-113069.md) | High | Chromium CVE-2026-113069: Memory corruption | 8.8 | 0.0030 | | | [CVE-2026-113311](https://patchblox.com/security/data/cve/CVE-2026-113311.md) | High | Chromium CVE-2026-113311: Use after free | 8.8 | 0.0030 | | | [CVE-2026-113059](https://patchblox.com/security/data/cve/CVE-2026-113059.md) | High | Chromium CVE-2026-113059: Memory corruption | 8.8 | 0.0030 | | | [CVE-2026-118316](https://patchblox.com/security/data/cve/CVE-2026-118316.md) | High | Chromium: CVE-2026-118316 Improper input validation in V8 | 9.6 | 0.0030 | | | [CVE-2026-118332](https://patchblox.com/security/data/cve/CVE-2026-118332.md) | High | Chromium: CVE-2026-118332 Improper input validation in Compositing | 9.6 | 0.0030 | | | [CVE-2026-118342](https://patchblox.com/security/data/cve/CVE-2026-118342.md) | High | Chromium: CVE-2026-118342 Out of bounds write in Editing | 9.6 | 0.0030 | | | [CVE-2026-118355](https://patchblox.com/security/data/cve/CVE-2026-118355.md) | High | Chromium: CVE-2026-118355 Improper input validation in Command | 9.6 | 0.0030 | | | [CVE-2026-76025](https://patchblox.com/security/data/cve/CVE-2026-76025.md) | High | Chromium CVE-2026-76025: Use after free | 8.8 | 0.0029 | | | [CVE-2026-113118](https://patchblox.com/security/data/cve/CVE-2026-113118.md) | High | Chromium CVE-2026-113118: Memory corruption | 8.8 | 0.0029 | | | [CVE-2026-113228](https://patchblox.com/security/data/cve/CVE-2026-113228.md) | High | Chromium CVE-2026-113228: Use after free | 8.8 | 0.0029 | | | [CVE-2026-113057](https://patchblox.com/security/data/cve/CVE-2026-113057.md) | High | Chromium CVE-2026-113057: Improper access control | 8.8 | 0.0029 | | | [CVE-2026-118315](https://patchblox.com/security/data/cve/CVE-2026-118315.md) | High | Chromium: CVE-2026-118315 Improper input validation in SVG | 8.8 | 0.0029 | | | [CVE-2026-118350](https://patchblox.com/security/data/cve/CVE-2026-118350.md) | High | Chromium: CVE-2026-118350 Use after free in Turbolev | 8.8 | 0.0029 | | | [CVE-2026-113231](https://patchblox.com/security/data/cve/CVE-2026-113231.md) | High | Chromium CVE-2026-113231: Improper input validation | 8.8 | 0.0028 | | | [CVE-2026-118357](https://patchblox.com/security/data/cve/CVE-2026-118357.md) | High | Chromium: CVE-2026-118357 Use after free in FileSystem | 8.8 | 0.0028 | | | [CVE-2026-118359](https://patchblox.com/security/data/cve/CVE-2026-118359.md) | High | Chromium: CVE-2026-118359 Memory corruption in V8 | 8.8 | 0.0028 | | | [CVE-2026-113016](https://patchblox.com/security/data/cve/CVE-2026-113016.md) | High | Chromium CVE-2026-113016: Improper input validation | 8.8 | 0.0028 | | | [CVE-2026-113136](https://patchblox.com/security/data/cve/CVE-2026-113136.md) | High | Chromium CVE-2026-113136: Memory corruption | 8.8 | 0.0028 | | | [CVE-2026-113150](https://patchblox.com/security/data/cve/CVE-2026-113150.md) | High | Chromium CVE-2026-113150: Memory corruption | 8.8 | 0.0028 | | | [CVE-2026-119262](https://patchblox.com/security/data/cve/CVE-2026-119262.md) | High | Chromium CVE-2026-119262: Improper input validation | 8.8 | 0.0028 | | | [CVE-2026-113008](https://patchblox.com/security/data/cve/CVE-2026-113008.md) | High | Chromium CVE-2026-113008: Memory corruption | 8.8 | 0.0028 | | | [CVE-2026-113041](https://patchblox.com/security/data/cve/CVE-2026-113041.md) | High | Chromium CVE-2026-113041: Use after free | 8.8 | 0.0028 | | | [CVE-2026-113115](https://patchblox.com/security/data/cve/CVE-2026-113115.md) | High | Chromium CVE-2026-113115: Use after free | 8.8 | 0.0028 | | | [CVE-2026-113137](https://patchblox.com/security/data/cve/CVE-2026-113137.md) | High | Chromium CVE-2026-113137: Memory corruption | 8.8 | 0.0028 | | | [CVE-2026-113048](https://patchblox.com/security/data/cve/CVE-2026-113048.md) | High | Chromium CVE-2026-113048: Memory corruption | 8.8 | 0.0028 | | | [CVE-2026-113075](https://patchblox.com/security/data/cve/CVE-2026-113075.md) | High | Chromium CVE-2026-113075: Use after free | 8.8 | 0.0028 | | | [CVE-2026-118304](https://patchblox.com/security/data/cve/CVE-2026-118304.md) | High | Chromium: CVE-2026-118304 Improper input validation in SVG | 8.8 | 0.0028 | | | [CVE-2026-118311](https://patchblox.com/security/data/cve/CVE-2026-118311.md) | High | Chromium: CVE-2026-118311 Memory corruption in Media | 8.8 | 0.0028 | | | [CVE-2026-118313](https://patchblox.com/security/data/cve/CVE-2026-118313.md) | High | Chromium: CVE-2026-118313 Use after free in Video | 8.8 | 0.0028 | | | [CVE-2026-118345](https://patchblox.com/security/data/cve/CVE-2026-118345.md) | High | Chromium: CVE-2026-118345 Use after free in PDFium | 8.8 | 0.0027 | | | [CVE-2026-113218](https://patchblox.com/security/data/cve/CVE-2026-113218.md) | High | Chromium CVE-2026-113218: Use after free | 8.8 | 0.0027 | | | [CVE-2026-119263](https://patchblox.com/security/data/cve/CVE-2026-119263.md) | High | Chromium CVE-2026-119263: Memory corruption | 9.6 | 0.0027 | | | [CVE-2026-113335](https://patchblox.com/security/data/cve/CVE-2026-113335.md) | High | Chromium CVE-2026-113335: Memory corruption | 8.8 | 0.0027 | | | [CVE-2026-113141](https://patchblox.com/security/data/cve/CVE-2026-113141.md) | High | Chromium CVE-2026-113141: Use after free | 8.8 | 0.0027 | | | [CVE-2026-113060](https://patchblox.com/security/data/cve/CVE-2026-113060.md) | High | Chromium CVE-2026-113060: Improper input validation | 8.8 | 0.0027 | | | [CVE-2026-118340](https://patchblox.com/security/data/cve/CVE-2026-118340.md) | High | Chromium: CVE-2026-118340 Memory corruption in Skia | 9.6 | 0.0027 | | | [CVE-2026-118328](https://patchblox.com/security/data/cve/CVE-2026-118328.md) | High | Chromium: CVE-2026-118328 Improper input validation in WebRTC | 8.8 | 0.0027 | | | [CVE-2026-118351](https://patchblox.com/security/data/cve/CVE-2026-118351.md) | High | Chromium: CVE-2026-118351 Memory corruption in Skia | 9.6 | 0.0026 | | | [CVE-2026-118334](https://patchblox.com/security/data/cve/CVE-2026-118334.md) | High | Chromium: CVE-2026-118334 Use after free in ImageCapture | 8.8 | 0.0026 | | | [CVE-2026-118341](https://patchblox.com/security/data/cve/CVE-2026-118341.md) | High | Chromium: CVE-2026-118341 Use after free in Modularization | 8.8 | 0.0026 | | | [CVE-2026-118343](https://patchblox.com/security/data/cve/CVE-2026-118343.md) | High | Chromium: CVE-2026-118343 Improper input validation in ReadingList | 8.8 | 0.0026 | | | [CVE-2026-118347](https://patchblox.com/security/data/cve/CVE-2026-118347.md) | High | Chromium: CVE-2026-118347 Use after free in FileSystem | 8.8 | 0.0026 | | | [CVE-2026-118349](https://patchblox.com/security/data/cve/CVE-2026-118349.md) | High | Chromium: CVE-2026-118349 Memory corruption in Payments | 8.8 | 0.0026 | | | [CVE-2026-118352](https://patchblox.com/security/data/cve/CVE-2026-118352.md) | High | Chromium: CVE-2026-118352 Memory corruption in Cache | 8.8 | 0.0026 | | | [CVE-2026-118356](https://patchblox.com/security/data/cve/CVE-2026-118356.md) | High | Chromium: CVE-2026-118356 Use after free in WTF | 8.8 | 0.0026 | | | [CVE-2026-119266](https://patchblox.com/security/data/cve/CVE-2026-119266.md) | High | Chromium CVE-2026-119266: Use after free | 8.8 | 0.0026 | | | [CVE-2026-113344](https://patchblox.com/security/data/cve/CVE-2026-113344.md) | High | Chromium CVE-2026-113344: Use after free | 8.8 | 0.0026 | | | [CVE-2026-76031](https://patchblox.com/security/data/cve/CVE-2026-76031.md) | High | Chromium CVE-2026-76031: Use after free | 8.8 | 0.0026 | | | [CVE-2026-113186](https://patchblox.com/security/data/cve/CVE-2026-113186.md) | High | Chromium CVE-2026-113186: Memory corruption | 9.6 | 0.0026 | | | [CVE-2026-113103](https://patchblox.com/security/data/cve/CVE-2026-113103.md) | High | Chromium CVE-2026-113103: Use after free | 8.8 | 0.0025 | | | [CVE-2026-118320](https://patchblox.com/security/data/cve/CVE-2026-118320.md) | High | Chromium: CVE-2026-118320 Memory corruption in V8 | 8.8 | 0.0025 | | | [CVE-2026-118336](https://patchblox.com/security/data/cve/CVE-2026-118336.md) | High | Chromium: CVE-2026-118336 Improper input validation in Headless | 8.8 | 0.0025 | | | [CVE-2026-118333](https://patchblox.com/security/data/cve/CVE-2026-118333.md) | High | Chromium: CVE-2026-118333 Missing authorization in Video | 9.3 | 0.0025 | | | [CVE-2026-113116](https://patchblox.com/security/data/cve/CVE-2026-113116.md) | High | Chromium CVE-2026-113116: Use after free | 9.6 | 0.0025 | | | [CVE-2026-113112](https://patchblox.com/security/data/cve/CVE-2026-113112.md) | High | Chromium CVE-2026-113112: Use after free | 8.8 | 0.0025 | | | [CVE-2026-113064](https://patchblox.com/security/data/cve/CVE-2026-113064.md) | High | Chromium CVE-2026-113064: Memory corruption | 8.8 | 0.0025 | | | [CVE-2026-119260](https://patchblox.com/security/data/cve/CVE-2026-119260.md) | High | Chromium CVE-2026-119260: Use after free | 8.8 | 0.0024 | | | [CVE-2026-119264](https://patchblox.com/security/data/cve/CVE-2026-119264.md) | High | Chromium CVE-2026-119264: Memory corruption | 8.8 | 0.0024 | | | [CVE-2026-119267](https://patchblox.com/security/data/cve/CVE-2026-119267.md) | High | Chromium CVE-2026-119267: Memory corruption | 8.8 | 0.0024 | | | [CVE-2026-119268](https://patchblox.com/security/data/cve/CVE-2026-119268.md) | High | Chromium CVE-2026-119268: Integer overflow | 8.8 | 0.0024 | | | [CVE-2026-118354](https://patchblox.com/security/data/cve/CVE-2026-118354.md) | High | Chromium: CVE-2026-118354 Improper input validation in Skia | 9.6 | 0.0024 | | | [CVE-2026-113119](https://patchblox.com/security/data/cve/CVE-2026-113119.md) | High | Chromium CVE-2026-113119: Use after free | 8.8 | 0.0023 | | | [CVE-2026-76028](https://patchblox.com/security/data/cve/CVE-2026-76028.md) | High | Chromium CVE-2026-76028: Use after free | 8.8 | 0.0023 | | | [CVE-2026-76030](https://patchblox.com/security/data/cve/CVE-2026-76030.md) | High | Chromium CVE-2026-76030: Memory corruption | 8.8 | 0.0023 | | | [CVE-2026-118312](https://patchblox.com/security/data/cve/CVE-2026-118312.md) | High | Chromium: CVE-2026-118312 Memory corruption in Paint | 9.6 | 0.0023 | | | [CVE-2026-119270](https://patchblox.com/security/data/cve/CVE-2026-119270.md) | High | Chromium CVE-2026-119270: Improper input validation | 8.8 | 0.0023 | | | [CVE-2026-118337](https://patchblox.com/security/data/cve/CVE-2026-118337.md) | High | Chromium: CVE-2026-118337 Improper access control in Forms | 9.3 | 0.0023 | | | [CVE-2026-118322](https://patchblox.com/security/data/cve/CVE-2026-118322.md) | High | Chromium: CVE-2026-118322 Memory corruption in ANGLE | 8.8 | 0.0022 | | | [CVE-2026-119265](https://patchblox.com/security/data/cve/CVE-2026-119265.md) | High | Chromium CVE-2026-119265: Memory corruption | 8.8 | 0.0022 | | | [CVE-2026-76029](https://patchblox.com/security/data/cve/CVE-2026-76029.md) | High | Chromium CVE-2026-76029: Memory corruption | 8.8 | 0.0022 | | | [CVE-2026-113229](https://patchblox.com/security/data/cve/CVE-2026-113229.md) | High | Chromium CVE-2026-113229: Use after free | 8.8 | 0.0022 | | | [CVE-2026-118327](https://patchblox.com/security/data/cve/CVE-2026-118327.md) | High | Chromium: CVE-2026-118327 Memory corruption in Media | 8.8 | 0.0022 | | | [CVE-2026-118338](https://patchblox.com/security/data/cve/CVE-2026-118338.md) | High | Chromium: CVE-2026-118338 Use after free in Animation | 8.8 | 0.0022 | | | [CVE-2026-118346](https://patchblox.com/security/data/cve/CVE-2026-118346.md) | High | Chromium: CVE-2026-118346 Use after free in Compositing | 8.8 | 0.0022 | | | [CVE-2026-119271](https://patchblox.com/security/data/cve/CVE-2026-119271.md) | High | Chromium CVE-2026-119271: Use after free | 9.6 | 0.0022 | | | [CVE-2026-118353](https://patchblox.com/security/data/cve/CVE-2026-118353.md) | High | Chromium: CVE-2026-118353 Use after free in Paint | 8.8 | 0.0021 | | | [CVE-2026-118319](https://patchblox.com/security/data/cve/CVE-2026-118319.md) | High | Chromium: CVE-2026-118319 Memory corruption in Skia | 9.6 | 0.0021 | | | [CVE-2026-119269](https://patchblox.com/security/data/cve/CVE-2026-119269.md) | High | Chromium CVE-2026-119269: Use after free | 8.8 | 0.0021 | | | [CVE-2026-113205](https://patchblox.com/security/data/cve/CVE-2026-113205.md) | High | Chromium CVE-2026-113205: Use after free | 8.8 | 0.0017 | | | [CVE-2026-76026](https://patchblox.com/security/data/cve/CVE-2026-76026.md) | High | Chromium CVE-2026-76026: Memory corruption | 8.8 | 0.0017 | | | [CVE-2026-20942](https://patchblox.com/security/data/cve/CVE-2026-20942.md) | Routine | Microsoft Edge (Chromium-based) Spoofing Vulnerability | 4.3 | 0.0063 | | | [CVE-2026-113193](https://patchblox.com/security/data/cve/CVE-2026-113193.md) | Routine | Chromium CVE-2026-113193: Memory corruption | 6.5 | 0.0047 | | | [CVE-2026-113098](https://patchblox.com/security/data/cve/CVE-2026-113098.md) | Routine | Chromium CVE-2026-113098: Memory corruption | 6.5 | 0.0043 | | | [CVE-2026-113223](https://patchblox.com/security/data/cve/CVE-2026-113223.md) | Routine | Chromium CVE-2026-113223: Memory corruption | 6.5 | 0.0043 | | | [CVE-2026-113159](https://patchblox.com/security/data/cve/CVE-2026-113159.md) | Routine | Chromium CVE-2026-113159: Improper access control | 6.5 | 0.0042 | | | [CVE-2026-113295](https://patchblox.com/security/data/cve/CVE-2026-113295.md) | Routine | Chromium CVE-2026-113295: Out of bounds read | 6.5 | 0.0041 | | | [CVE-2026-113309](https://patchblox.com/security/data/cve/CVE-2026-113309.md) | Routine | Chromium CVE-2026-113309: Out of bounds read | 6.5 | 0.0041 | | | [CVE-2026-113326](https://patchblox.com/security/data/cve/CVE-2026-113326.md) | Routine | Chromium CVE-2026-113326: Memory corruption | 6.5 | 0.0041 | | | [CVE-2026-113157](https://patchblox.com/security/data/cve/CVE-2026-113157.md) | Routine | Chromium CVE-2026-113157: Information leak | 6.5 | 0.0037 | | | [CVE-2026-113322](https://patchblox.com/security/data/cve/CVE-2026-113322.md) | Routine | Chromium CVE-2026-113322: Memory corruption | 6.5 | 0.0037 | | | [CVE-2026-113340](https://patchblox.com/security/data/cve/CVE-2026-113340.md) | Routine | Chromium CVE-2026-113340: Memory corruption | 6.5 | 0.0037 | | | [CVE-2026-113035](https://patchblox.com/security/data/cve/CVE-2026-113035.md) | Routine | Chromium CVE-2026-113035: Out of bounds read | 6.5 | 0.0036 | | | [CVE-2026-113070](https://patchblox.com/security/data/cve/CVE-2026-113070.md) | Routine | Chromium CVE-2026-113070: Out of bounds read | 6.5 | 0.0036 | | | [CVE-2026-113066](https://patchblox.com/security/data/cve/CVE-2026-113066.md) | Routine | Chromium CVE-2026-113066: Memory corruption | 6.5 | 0.0036 | | | [CVE-2026-113102](https://patchblox.com/security/data/cve/CVE-2026-113102.md) | Routine | Chromium CVE-2026-113102: Out of bounds read | 6.5 | 0.0036 | | | [CVE-2026-113010](https://patchblox.com/security/data/cve/CVE-2026-113010.md) | Routine | Chromium CVE-2026-113010: Out of bounds read | 6.5 | 0.0036 | | | [CVE-2026-113142](https://patchblox.com/security/data/cve/CVE-2026-113142.md) | Routine | Chromium CVE-2026-113142: Memory corruption | 6.5 | 0.0034 | | | [CVE-2026-113297](https://patchblox.com/security/data/cve/CVE-2026-113297.md) | Routine | Chromium CVE-2026-113297: Improper access control | 6.5 | 0.0034 | | | [CVE-2026-113122](https://patchblox.com/security/data/cve/CVE-2026-113122.md) | Routine | Chromium CVE-2026-113122: Memory corruption | 6.5 | 0.0034 | | | [CVE-2026-113047](https://patchblox.com/security/data/cve/CVE-2026-113047.md) | Routine | Chromium CVE-2026-113047: Memory corruption | 6.5 | 0.0034 | | | [CVE-2026-113296](https://patchblox.com/security/data/cve/CVE-2026-113296.md) | Routine | Chromium CVE-2026-113296: Memory corruption | 6.5 | 0.0033 | | | [CVE-2026-113199](https://patchblox.com/security/data/cve/CVE-2026-113199.md) | Routine | Chromium CVE-2026-113199: Out of bounds read | 6.5 | 0.0032 | | | [CVE-2026-113201](https://patchblox.com/security/data/cve/CVE-2026-113201.md) | Routine | Chromium CVE-2026-113201: Memory corruption | 6.5 | 0.0032 | | | [CVE-2026-113054](https://patchblox.com/security/data/cve/CVE-2026-113054.md) | Routine | Chromium CVE-2026-113054: Out of bounds read | 6.5 | 0.0032 | | | [CVE-2026-113151](https://patchblox.com/security/data/cve/CVE-2026-113151.md) | Routine | Chromium CVE-2026-113151: Out of bounds read | 6.5 | 0.0032 | | | [CVE-2026-113002](https://patchblox.com/security/data/cve/CVE-2026-113002.md) | Routine | Chromium CVE-2026-113002: Memory corruption | 6.5 | 0.0032 | | | [CVE-2026-113050](https://patchblox.com/security/data/cve/CVE-2026-113050.md) | Routine | Chromium CVE-2026-113050: Out of bounds read | 6.5 | 0.0032 | | | [CVE-2026-113310](https://patchblox.com/security/data/cve/CVE-2026-113310.md) | Routine | Chromium CVE-2026-113310: Out of bounds read | 6.5 | 0.0032 | | | [CVE-2026-113051](https://patchblox.com/security/data/cve/CVE-2026-113051.md) | Routine | Chromium CVE-2026-113051: Memory corruption | 6.5 | 0.0031 | | | [CVE-2026-113082](https://patchblox.com/security/data/cve/CVE-2026-113082.md) | Routine | Chromium CVE-2026-113082: Memory corruption | 6.5 | 0.0030 | | | [CVE-2026-113139](https://patchblox.com/security/data/cve/CVE-2026-113139.md) | Routine | Chromium CVE-2026-113139: Memory corruption | 6.5 | 0.0030 | | | [CVE-2026-113144](https://patchblox.com/security/data/cve/CVE-2026-113144.md) | Routine | Chromium CVE-2026-113144: Memory corruption | 6.5 | 0.0030 | | | [CVE-2026-88078](https://patchblox.com/security/data/cve/CVE-2026-88078.md) | Routine | Microsoft Edge (Chromium-based) Spoofing Vulnerability | 4.3 | 0.0029 | | | [CVE-2026-118318](https://patchblox.com/security/data/cve/CVE-2026-118318.md) | Routine | Chromium: CVE-2026-118318 Improper access control in V8 | 4.3 | 0.0028 | | | [CVE-2026-113129](https://patchblox.com/security/data/cve/CVE-2026-113129.md) | Routine | Chromium CVE-2026-113129: Improper access control | 6.5 | 0.0027 | | | [CVE-2026-113038](https://patchblox.com/security/data/cve/CVE-2026-113038.md) | Routine | Chromium CVE-2026-113038: Memory corruption | 6.5 | 0.0027 | | | [CVE-2026-113237](https://patchblox.com/security/data/cve/CVE-2026-113237.md) | Routine | Chromium CVE-2026-113237: Memory corruption | 6.5 | 0.0025 | | | [CVE-2026-113333](https://patchblox.com/security/data/cve/CVE-2026-113333.md) | Routine | Chromium CVE-2026-113333: Memory corruption | 6.5 | 0.0025 | | | [CVE-2026-76027](https://patchblox.com/security/data/cve/CVE-2026-76027.md) | Routine | Chromium CVE-2026-76027: Memory corruption | 4.3 | 0.0023 | | | [CVE-2026-119272](https://patchblox.com/security/data/cve/CVE-2026-119272.md) | Routine | Chromium CVE-2026-119272: Out of bounds read | 4.3 | 0.0016 | | --- Data as of 2026-11-10T13:56:55Z 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.