CVE-2016-0010 — Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office 2016,...

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Excel For Mac, Microsoft Office, Microsoft Powerpoint For Mac…).
2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
4. EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-119 · Buffer Errors (Improper Restriction of Operations within Memory Bounds)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
• Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.

Timeline

What happened to this CVE, newest first.

• 2026
• SSVC assessment updated
  Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 15, 2026
• Affected products added · microsoft/excel for mac, microsoft/office, microsoft/powerpoint for mac, microsoft/word for mac, microsoft/word viewer
  Oct 15, 2026 · NIST National Vulnerability Database
• CVSS changed · 7.8
  Oct 15, 2026 · NIST National Vulnerability Database
• Source status changed · → Modified
  Oct 15, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 15, 2026 · Alertas do Telegram
• 2016
• CVE published
  Jan 13, 2016 · microsoft

Source activity

Repeated readings are counted rather than listed.

• 2× References added · Oct 15, 2026 – Oct 15, 2026
• 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

4 on the record

• github.com/advisories/GHSA-3m2q-3xcm-4xxf
  GitHub Security Advisories
• nvd.nist.gov/vuln/detail/CVE-2016-0010
  GitHub Security Advisories
• www.securitytracker.com/id/1034651
  vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
• docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-004
  vendor-advisory, x_refsource_MS, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-47293 Microsoft Office Click-To-Run Elevation of Privilege Vulnerability Jun 9, 2026
• Medium CVE-2026-42832 Microsoft Office Spoofing Vulnerability May 12, 2026
• High CVE-2026-42831 Microsoft Office Remote Code Execution Vulnerability May 12, 2026
• High CVE-2026-40420 Microsoft Office Click-To-Run Elevation of Privilege Vulnerability May 12, 2026
• High CVE-2026-40419 Microsoft Office Click-To-Run Elevation of Privilege Vulnerability May 12, 2026
• Medium CVE-2026-40421 Microsoft Word Information Disclosure Vulnerability May 12, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2016-0010 is "Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office 2016,...", rated High. It affects Excel For Mac (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 21.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.