CVE Tools

CVE-2026-70317

Microsoft Office Information Disclosure Vulnerability

No known exploitation. EPSS puts it in the 35th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check which Microsoft Office product/version you run (Microsoft 365 apps, Microsoft Office, Microsoft Office for Mac, or Office LTSC for Mac 2021/2024) and whether it’s at or above the fixed versions listed for CVE-2026-70317.
  2. If you’re not fully updated, upgrade Office to the fixed release for your product: Microsoft Office fixed in 16.0.5565.1001, and macOS fixed in 16.112.26081010.
  3. Verify updates actually applied on each managed device (especially staff laptops/desktops), then confirm Office opens normally with your usual document types.
  4. Reduce the chance of a “crafted document” getting opened: keep Office security settings enabled and train staff not to open unexpected attachments or files from untrusted sources.

What it is

From the CVE record

Use of uninitialized resource in Microsoft Office allows an unauthorized attacker to disclose information locally.

In plain language

Written by AI from the record

This Microsoft Office flaw can reveal some sensitive information only if someone already has access to your computer and gets you to open a specially made Office file. For most small businesses, it’s not an everyday risk—but it’s worth fixing because attackers may target staff devices.

CVE-2026-70317 is an information disclosure issue in Microsoft Office caused by improper initialization of certain resources; a local attacker can trigger it by persuading a user to open a crafted Office document, leading to unintended disclosure of local information.

If you're affected

  • Local sensitive data exposure
  • User device compromise impact
  • Document confidentiality loss
  • Privacy and compliance risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS35th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 35th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 3 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Scored 5.5 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store