CVE-2017-11826 · Published 13 Oct 2017
Microsoft Office
On CISA's KEV list 1602 days after disclosure; 1 public exploit.
A remote code execution vulnerability exists in Microsoft Office software when the software fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user.
CISA required action (federal due date 24 Mar 2022): Apply updates per vendor instructions.
Signals
- KEV, exploited in the wild
- yes, added 3 Mar 2022, due 24 Mar 2022
- EPSS, 30-day forecast
- 82%, 100th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 13 Oct 2017 to today
- Disclosed
- KEV+1602 d
1,602 days from disclosure to the KEV listing
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 1 known · links only
GitHub PoCs 1Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars1
- thatskriptkid/CVE-2017-11826Not checked
first seen by skopnix 18 Oct 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.