Code execution via undisclosed buffer over-read
Published May 13, 2025 · Updated Feb 26, 2026
Buffer over-read in Microsoft Excel in affected Office releases allows local users to execute arbitrary code through locally supplied data. Excel reads beyond the end of an internal buffer while processing untrusted data, but Microsoft has not disclosed the parser, file format, or function involved. The attack requires access to invoke Excel with attacker-controlled data; successful exploitation runs code in the affected process context.
Summary
What happened
Buffer over-read in Microsoft Excel in affected Office releases allows local users to execute arbitrary code through locally supplied data. Excel reads beyond the end of an internal buffer while processing untrusted data, but Microsoft has not disclosed the parser, file format, or function involved. The attack requires access to invoke Excel with attacker-controlled data; successful exploitation runs code in the affected process context.
The record
- CVE
- CVE-2025-32704
- Published
- May 13, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office 2019
- Classifications
- CWE-125, CWE-126, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=19.0.0 <https://aka.ms/OfficeSecurityReleases
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo