Code execution via untrusted pointer dereference
Published Jan 13, 2026 · Updated Jan 13, 2026
Untrusted pointer dereference in Microsoft Excel allows attackers to execute code locally after opening a crafted workbook. Microsoft identifies the flaw only as an untrusted pointer dereference and has not disclosed the affected Excel code path or pointer operation. Successful exploitation requires a user to open the crafted file and runs attacker-controlled code in the user's security context across the listed Office clients and Office Online Server.
Summary
What happened
Untrusted pointer dereference in Microsoft Excel allows attackers to execute code locally after opening a crafted workbook. Microsoft identifies the flaw only as an untrusted pointer dereference and has not disclosed the affected Excel code path or pointer operation. Successful exploitation requires a user to open the crafted file and runs attacker-controlled code in the user's security context across the listed Office clients and Office Online Server.
The record
- CVE
- CVE-2026-20955
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-822, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 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.105.26011018
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