# Microsoft Edge 154.0.4258.62

Microsoft Edge 154.0.4258.62, released October 5, 2026, fixes 38 CVEs in Microsoft Edge. One of them is being exploited (CVE-2026-96951); 1 on CISA KEV. Patch Radar priority: Patch now. The latest Microsoft Edge is 156.0.4314.58, which also fixes every one of these CVEs.

- Web page: https://patchblox.com/security/fix/windows-app/microsoft.edge-154.0.4258.62
- Platform: Windows apps
- Released: Oct 5, 2026
- Priority: Patch now (Closes CVE-2026-96951, exploited (CISA KEV))
- CVEs: 38, exploited: 1, on CISA KEV: 1
- Superseded by: [Microsoft Edge 156.0.4314.58](https://patchblox.com/security/data/product/windows-app/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/windows-app/microsoft-edge.md) |  | 154.0.4258.62 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2026-96951](https://patchblox.com/security/data/cve/CVE-2026-96951.md) | Patch now | Windows Shell Security Feature Bypass Vulnerability | 8.8 | 0.0981 | CISA KEV |
| [CVE-2026-103628](https://patchblox.com/security/data/cve/CVE-2026-103628.md) | Urgent | Chromium CVE-2026-103628: Out of bounds write | 9.6 | 0.0038 |  |
| [CVE-2026-103626](https://patchblox.com/security/data/cve/CVE-2026-103626.md) | Urgent | Chromium CVE-2026-103626: Incorrect authorization | 9.6 | 0.0033 |  |
| [CVE-2026-103630](https://patchblox.com/security/data/cve/CVE-2026-103630.md) | Urgent | Chromium CVE-2026-103630: Use after free | 9.6 | 0.0033 |  |
| [CVE-2026-88077](https://patchblox.com/security/data/cve/CVE-2026-88077.md) | High | Microsoft Edge (Chromium-based) Elevation of Privilege Vulnerability | 8.8 | 0.0063 |  |
| [CVE-2026-103631](https://patchblox.com/security/data/cve/CVE-2026-103631.md) | High | Chromium CVE-2026-103631: Buffer overflow | 8.8 | 0.0046 |  |
| [CVE-2026-102299](https://patchblox.com/security/data/cve/CVE-2026-102299.md) | High | Chromium CVE-2026-102299: Type confusion | 8.8 | 0.0042 |  |
| [CVE-2026-102323](https://patchblox.com/security/data/cve/CVE-2026-102323.md) | High | Chromium CVE-2026-102323: Type confusion | 8.8 | 0.0042 |  |
| [CVE-2026-102306](https://patchblox.com/security/data/cve/CVE-2026-102306.md) | High | Chromium CVE-2026-102306: Use after free | 9.6 | 0.0038 |  |
| [CVE-2026-102302](https://patchblox.com/security/data/cve/CVE-2026-102302.md) | High | Chromium CVE-2026-102302: Buffer overflow | 8.8 | 0.0036 |  |
| [CVE-2026-102321](https://patchblox.com/security/data/cve/CVE-2026-102321.md) | High | Chromium CVE-2026-102321: Type confusion | 8.8 | 0.0034 |  |
| [CVE-2026-102328](https://patchblox.com/security/data/cve/CVE-2026-102328.md) | High | Chromium CVE-2026-102328: Type confusion | 8.8 | 0.0033 |  |
| [CVE-2026-102326](https://patchblox.com/security/data/cve/CVE-2026-102326.md) | High | Chromium CVE-2026-102326: Type confusion | 8.8 | 0.0033 |  |
| [CVE-2026-103625](https://patchblox.com/security/data/cve/CVE-2026-103625.md) | High | Chromium CVE-2026-103625: Type confusion | 8.8 | 0.0032 |  |
| [CVE-2026-102304](https://patchblox.com/security/data/cve/CVE-2026-102304.md) | High | Chromium CVE-2026-102304: Use after free | 9.6 | 0.0032 |  |
| [CVE-2026-102308](https://patchblox.com/security/data/cve/CVE-2026-102308.md) | High | Chromium CVE-2026-102308: Use after free | 9.6 | 0.0032 |  |
| [CVE-2026-102309](https://patchblox.com/security/data/cve/CVE-2026-102309.md) | High | Chromium CVE-2026-102309: Use after free | 9.6 | 0.0032 |  |
| [CVE-2026-102316](https://patchblox.com/security/data/cve/CVE-2026-102316.md) | High | Chromium CVE-2026-102316: Use after free | 9.6 | 0.0031 |  |
| [CVE-2026-103622](https://patchblox.com/security/data/cve/CVE-2026-103622.md) | High | Chromium CVE-2026-103622: Use after free | 8.8 | 0.0031 |  |
| [CVE-2026-103623](https://patchblox.com/security/data/cve/CVE-2026-103623.md) | High | Chromium CVE-2026-103623: Use after free | 8.8 | 0.0030 |  |
| [CVE-2026-102301](https://patchblox.com/security/data/cve/CVE-2026-102301.md) | High | Chromium CVE-2026-102301: Out of bounds write | 8.3 | 0.0029 |  |
| [CVE-2026-103624](https://patchblox.com/security/data/cve/CVE-2026-103624.md) | High | Chromium CVE-2026-103624: Use after free | 8.3 | 0.0028 |  |
| [CVE-2026-102324](https://patchblox.com/security/data/cve/CVE-2026-102324.md) | High | Chromium CVE-2026-102324: Use after free | 8.3 | 0.0027 |  |
| [CVE-2026-102325](https://patchblox.com/security/data/cve/CVE-2026-102325.md) | High | Chromium CVE-2026-102325: Uninitialized resource | 9.6 | 0.0023 |  |
| [CVE-2026-103629](https://patchblox.com/security/data/cve/CVE-2026-103629.md) | High | Chromium CVE-2026-103629: Integer overflow | 9.6 | 0.0020 |  |
| [CVE-2026-102317](https://patchblox.com/security/data/cve/CVE-2026-102317.md) | High | Chromium CVE-2026-102317: Improper privilege management | 8.6 | 0.0011 |  |
| [CVE-2026-102313](https://patchblox.com/security/data/cve/CVE-2026-102313.md) | Routine | Chromium CVE-2026-102313: Uninitialized resource | 4.7 | 0.0028 |  |
| [CVE-2026-102300](https://patchblox.com/security/data/cve/CVE-2026-102300.md) | Routine | Chromium CVE-2026-102300: Uninitialized resource in WebGPU | 4.3 | 0.0028 |  |
| [CVE-2026-103627](https://patchblox.com/security/data/cve/CVE-2026-103627.md) | Routine | Chromium CVE-2026-103627: Information leak | 6.5 | 0.0025 |  |
| [CVE-2026-102310](https://patchblox.com/security/data/cve/CVE-2026-102310.md) | Routine | Chromium CVE-2026-102310: Missing authorization | 6.5 | 0.0024 |  |
| [CVE-2026-102320](https://patchblox.com/security/data/cve/CVE-2026-102320.md) | Routine | Chromium CVE-2026-102320: Missing authorization | 6.5 | 0.0023 |  |
| [CVE-2026-102330](https://patchblox.com/security/data/cve/CVE-2026-102330.md) | Routine | Chromium CVE-2026-102330: Incorrect authorization | 6.5 | 0.0023 |  |
| [CVE-2026-102318](https://patchblox.com/security/data/cve/CVE-2026-102318.md) | Routine | Chromium CVE-2026-102318: Out of bounds read | 4.7 | 0.0021 |  |
| [CVE-2026-102315](https://patchblox.com/security/data/cve/CVE-2026-102315.md) | Routine | Chromium CVE-2026-102315: Uninitialized resource | 3.4 | 0.0021 |  |
| [CVE-2026-102319](https://patchblox.com/security/data/cve/CVE-2026-102319.md) | Routine | Chromium CVE-2026-102319: Uninitialized resource | 3.4 | 0.0021 |  |
| [CVE-2026-102314](https://patchblox.com/security/data/cve/CVE-2026-102314.md) | Routine | Chromium CVE-2026-102314: UI misrepresentation | 5.4 | 0.0021 |  |
| [CVE-2026-103621](https://patchblox.com/security/data/cve/CVE-2026-103621.md) | Routine | Chromium CVE-2026-103621: Integer overflow | 4.3 | 0.0020 |  |
| [CVE-2026-102329](https://patchblox.com/security/data/cve/CVE-2026-102329.md) | Routine | Chromium CVE-2026-102329: Cross-site scripting | 6.1 | 0.0018 |  |

---

Data as of 2026-11-11T07:45:43Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
