CVE-2017-0260 — A remote code execution vulnerability exists in Microsoft Office when the software fails to...

Triage

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

Remediation

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

• Documented patch — portal.msrc.microsoft.com (NIST National Vulnerability Database)

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 Office, Microsoft Windows 7, Microsoft Windows Server 2008).
2. Apply the fixed version or the patch documented under Remediation.
3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
4. EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
5. Search available logs for exploit probes, 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.

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.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · microsoft corporation/microsoft office
  Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 15, 2026
• Fix documented
  Oct 15, 2026 · NIST National Vulnerability Database
• Affected products added · microsoft/office, microsoft/windows 7, microsoft/windows server 2008
  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
• 2017
• CVE published
  Jun 14, 2017 · 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

5 on the record

• portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0260
  Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
• www.securitytracker.com/id/1038668
  vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
• nvd.nist.gov/vuln/detail/CVE-2017-0260
  GitHub Security Advisories
• www.securityfocus.com/bid/98810
  Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database
• github.com/advisories/GHSA-4948-3w2r-3h9p
  GitHub Security Advisories

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-40419 Microsoft Office Click-To-Run Elevation of Privilege Vulnerability May 12, 2026
• High CVE-2026-40420 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 CISA SSVC assessment.
• No CWE classification.
• 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-2017-0260 is "A remote code execution vulnerability exists in Microsoft Office when the software fails to...", rated High. It affects Office (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 19.94% 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.