CVE-2025-47165: Microsoft Excel Remote Code Execution Vulnerability
Noroxi assessment
Priority: Monitor (action score 32/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 83.4% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Use after free in Microsoft Office Excel allows an unauthorized attacker to execute code locally.
- Published
- Jun 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 2.2% · 83th percentile
- CWE
- CWE-416
Report tools
Action score
32
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | 365 apps | cpe:2.3:a:microsoft:365_apps |
| microsoft | excel | cpe:2.3:a:microsoft:excel |
| microsoft | office | cpe:2.3:a:microsoft:office |
| microsoft | office long term servicing channel | cpe:2.3:a:microsoft:office_long_term_servicing_channel |
| microsoft | office online server | cpe:2.3:a:microsoft:office_online_server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft 365 Apps for Enterprise
- 16.0.1 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Excel 2016
- 16.0.0.0 and later · before 16.0.5504.1000affected
Microsoft Microsoft Office 2019
- 19.0.0 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Office LTSC 2021
- 16.0.1 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Office LTSC 2024
- 16.0.0 and later · before https://aka.ms/OfficeSecurityReleasesaffected
Microsoft Microsoft Office LTSC for Mac 2021
- 16.0.1 and later · before 16.98.25060824affected
Microsoft Microsoft Office LTSC for Mac 2024
- 16.0.0 and later · before 16.98.25060824affected
Microsoft Office Online Server
- 16.0.0.0 and later · before 16.0.10417.20018affected
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft 365 appsall versions
- microsoft excel2016
- microsoft office2019
- microsoft office long term servicing channel2021
- microsoft office long term servicing channel2024
- microsoft office online serverbefore 16.0.10417.20018
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-23397Microsoft Outlook Elevation of Privilege VulnerabilityKEV98Now
- CVE-2024-21413Microsoft Outlook Remote Code Execution VulnerabilityKEV97Now
- CVE-2026-21509Microsoft Office Security Feature Bypass VulnerabilityKEV82Now
Published before and after this one in the same product
- ← EarlierCVE-2025-47162Jun 10, 2025 · Microsoft Office Remote Code Execution Vulnerability33Monitor
- ← EarlierCVE-2025-47164Jun 10, 2025 · Microsoft Office Remote Code Execution Vulnerability33Monitor
- Later →CVE-2025-47167Jun 10, 2025 · Microsoft Office Remote Code Execution Vulnerability33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2025-06-26 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+15 d
- TodayNov 12, 2026+520 d
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-88178490 days apartMicrosoft Office PowerPoint Remote Code Execution Vulnerability39Monitor
- CVE-2026-62870419 days apartMicrosoft Excel Remote Code Execution Vulnerability35Monitor
- CVE-2026-69767455 days apartMicrosoft Office PowerPoint Remote Code Execution Vulnerability35Monitor
- CVE-2026-78507455 days apartMicrosoft Office Word Remote Code Execution Vulnerability35Monitor
- CVE-2026-78514455 days apartMicrosoft Office Word Remote Code Execution Vulnerability35Monitor
- CVE-2026-78525455 days apartMicrosoft Office Outlook Remote Code Execution Vulnerability35Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.