# Microsoft Edge 155.0.4283.60 Microsoft Edge 155.0.4283.60, released October 15, 2026, fixes 39 CVEs in Microsoft Edge. None of them is reported as exploited. Patch Radar priority: Urgent. The latest Microsoft Edge is 157.0.4341.46, which also fixes every one of these CVEs. - Web page: https://patchblox.com/security/fix/macos/com.microsoft.edgemac-155.0.4283.60 - Platform: macOS - Released: Oct 15, 2026 - Priority: Urgent (Closes CVE-2026-110136, rated Critical) - CVEs: 39, exploited: 0, on CISA KEV: 0 - Superseded by: [Microsoft Edge 157.0.4341.46](https://patchblox.com/security/data/product/macos/microsoft-edge.md), the latest version, which also fixes every CVE listed here ## Applies to | Product | Release | Fixed in | |---|---|---| | [Microsoft Edge](https://patchblox.com/security/data/product/macos/microsoft-edge.md) | | 155.0.4283.60 | ## CVEs this fix closes | CVE | Priority | Title | CVSS | EPSS | Exploitation | |---|---|---|---:|---:|---| | [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-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-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-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-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-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-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-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-110166](https://patchblox.com/security/data/cve/CVE-2026-110166.md) | High | Chromium CVE-2026-110166: Buffer overflow | 8.8 | 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-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-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-110159](https://patchblox.com/security/data/cve/CVE-2026-110159.md) | High | Chromium CVE-2026-110159: Incorrect authorization | 9.6 | 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-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-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-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-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-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-110160](https://patchblox.com/security/data/cve/CVE-2026-110160.md) | Routine | Chromium CVE-2026-110160: Missing authorization | 4.2 | 0.0016 | | --- Data as of 2026-11-11T13:47:35Z 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.