CVE-2025-59243 json
Microsoft Excel Remote Code Execution Vulnerability
published last yr. modified 22d ago also EUVD-2025-34377
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
Use after free in Microsoft Office Excel allows an unauthorized attacker to execute code locally.
Patch / fix
Is CVE-2025-59243 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft 365 Apps for Enterprise
- Microsoft Microsoft Office LTSC 2021
- Microsoft Microsoft Office LTSC 2024
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2025-59243
vendor-advisory, patch
Sources
- CVE List CVE-2025-59243
- NVD CVE-2025-59243
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.