# Microsoft Edge Dev 138.0.3309.1

Microsoft Edge Dev 138.0.3309.1, released May 14, 2025, fixes 14 CVEs in Microsoft Edge Dev. One of them is being exploited (CVE-2025-5419); 1 on CISA KEV. Patch Radar priority: Patch now. 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-138.0.3309.1
- Platform: Windows apps
- Released: May 14, 2025
- Priority: Patch now (Closes CVE-2025-5419, exploited (CISA KEV))
- CVEs: 14, exploited: 1, on CISA KEV: 1
- 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) |  | 138.0.3309.1 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2025-5419](https://patchblox.com/security/data/cve/CVE-2025-5419.md) | Patch now | Chromium: CVE-2025-5419 Out of bounds read and write in V8 | 8.8 | 0.0755 | CISA KEV |
| [CVE-2025-5959](https://patchblox.com/security/data/cve/CVE-2025-5959.md) | High | Chromium: CVE-2025-5959 Type Confusion in V8 | 8.8 | 0.1278 |  |
| [CVE-2025-6191](https://patchblox.com/security/data/cve/CVE-2025-6191.md) | High | Chromium: CVE-2025-6191 Integer overflow in V8 | 8.8 | 0.1159 |  |
| [CVE-2025-5063](https://patchblox.com/security/data/cve/CVE-2025-5063.md) | High | Chromium: CVE-2025-5063 Use after free in Compositing | 8.8 | 0.0367 |  |
| [CVE-2025-5068](https://patchblox.com/security/data/cve/CVE-2025-5068.md) | High | Chromium: CVE-2025-5068 Use after free in Blink | 8.8 | 0.0347 |  |
| [CVE-2025-5280](https://patchblox.com/security/data/cve/CVE-2025-5280.md) | High | Chromium: CVE-2025-5280 Out of bounds write in V8 | 8.8 | 0.0291 |  |
| [CVE-2025-5283](https://patchblox.com/security/data/cve/CVE-2025-5283.md) | High | Chromium: CVE-2025-5283 Use after free in libvpx | 8.8 | 0.0064 |  |
| [CVE-2025-6192](https://patchblox.com/security/data/cve/CVE-2025-6192.md) | High | Chromium: CVE-2025-6192 Use after free in Profiler | 8.8 | 0.0045 |  |
| [CVE-2025-5958](https://patchblox.com/security/data/cve/CVE-2025-5958.md) | High | Chromium: CVE-2025-5958 Use after free in Media | 8.8 | 0.0039 |  |
| [CVE-2025-5065](https://patchblox.com/security/data/cve/CVE-2025-5065.md) | Routine | Chromium: CVE-2025-5065 Inappropriate implementation in FileSystemAccess API | 6.5 | 0.0041 |  |
| [CVE-2025-5066](https://patchblox.com/security/data/cve/CVE-2025-5066.md) | Routine | Chromium: CVE-2025-5066 Inappropriate implementation in Messages | 6.5 | 0.0041 |  |
| [CVE-2025-5067](https://patchblox.com/security/data/cve/CVE-2025-5067.md) | Routine | Chromium: CVE-2025-5067 Inappropriate implementation in Tab Strip | 5.4 | 0.0036 |  |
| [CVE-2025-5064](https://patchblox.com/security/data/cve/CVE-2025-5064.md) | Routine | Chromium: CVE-2025-5064 Inappropriate implementation in Background Fetch API | 5.4 | 0.0032 |  |
| [CVE-2025-5281](https://patchblox.com/security/data/cve/CVE-2025-5281.md) | Routine | Chromium: CVE-2025-5281 Inappropriate implementation in BFCache | 5.4 | 0.0024 |  |

---

Data as of 2026-11-10T20:03:11Z 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.