Security feature bypass after user interaction
Published Jan 14, 2025 · Updated Jun 9, 2026
A security feature bypass in Microsoft Office allows attackers to compromise integrity and availability after user interaction. Microsoft has not published the affected Office component, the security control bypassed, or how untrusted input reaches the flaw. Exploitation requires a local attack path and user interaction; the vendor reports no confidentiality impact, while successful exploitation can alter data or interrupt Office operation.
Summary
What happened
A security feature bypass in Microsoft Office allows attackers to compromise integrity and availability after user interaction. Microsoft has not published the affected Office component, the security control bypassed, or how untrusted input reaches the flaw. Exploitation requires a local attack path and user interaction; the vendor reports no confidentiality impact, while successful exploitation can alter data or interrupt Office operation.
The record
- CVE
- CVE-2025-21346
- Published
- Jan 14, 2025
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office 2016
- Classifications
- CWE-693
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 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=16.0.0 <16.0.5483.1001
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