cve.bz

CVE-2016-0012 microsoft

4.3 mediumEPSS 11%

Medium (4.3) in microsoft. EPSS 11% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft Office 2007 SP3, Excel 2007 SP3, PowerPoint 2007 SP3, Visio 2007 SP3, Word 2007 SP3, Office 2010 SP2, Excel 2010 SP2, PowerPoint 2010 SP2, Visio 2010 SP2, Word 2010 SP2, Office 2013 SP1, Excel 2013 SP1, PowerPoint 2013 SP1, Visio 2013 SP1, Word 2013 SP1, Excel 2013 RT SP1, PowerPoint 2013 RT SP1, Word 2013 RT SP1, Office 2016, Excel 2016, PowerPoint 2016, Visio 2016, Word 2016, and Visual Basic 6.0 Runtime allow remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "Microsoft Office ASLR Bypass."

Severity

CVSS 3.0

4.3 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
11% (unchanged from 11% a week ago; 11% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2016-0012 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-0012?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-0012?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2016-0012 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2016-0012

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2016-0012](https://cve.bz/cve/badge/CVE-2016-0012.svg)](https://cve.bz/cve/CVE-2016-0012)

HTML:

<a href="https://cve.bz/cve/CVE-2016-0012"><img src="https://cve.bz/cve/badge/CVE-2016-0012.svg" alt="CVE-2016-0012"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:excel2007:sp3
microsoft:excel2010:sp2
microsoft:excel2013:sp1
microsoft:excel2016
microsoft:office2007:sp3
microsoft:office2010:sp2
microsoft:office2013:sp1
microsoft:office2016
microsoft:powerpoint2010:sp2
microsoft:powerpoint2013:sp1
microsoft:powerpoint2016
microsoft:visio2007:sp3
microsoft:visio2010:sp2
microsoft:visio2013:sp1
microsoft:visio2016
microsoft:visual_basics6.0
microsoft:word2007:sp3
microsoft:word2010:sp2
microsoft:word2013:sp1
microsoft:word2016

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON