CVE Tools

CVE-2026-63524

Microsoft Office Information Disclosure Vulnerability

No known exploitation. EPSS puts it in the 43rd 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/Microsoft 365 version you run (Windows and/or Mac) and confirm whether you have any of these affected products installed: microsoft 365 apps, microsoft office, Microsoft Office 365 for Mac, Microsoft Office LTSC for Mac 2021, Microsoft Office LTSC for Mac 2024, microsoft 365, office 2016, office 2019, office 2021, office 2024.
  2. Update Microsoft Office on each device to the fixed version for your product.
  3. If you can’t update right away, restrict opening files from untrusted sources (especially email attachments and downloaded documents) until updates are applied.
  4. Review device logs for unusual Office file-opening activity tied to unexpected documents, and remove any suspicious files/sources from user access.

What it is

From the CVE record

Out-of-bounds read in Microsoft Office allows an unauthorized attacker to disclose information locally.

In plain language

Written by AI from the record

CVE-2026-63524 is a Microsoft Office bug that can expose confidential information if someone with local access gets you to open a specially made Office file; most small businesses should patch, but it’s not an automatic internet threat.

CVE-2026-63524 is a Microsoft Office information disclosure issue (CWE-125) triggered via user interaction when a locally positioned attacker delivers a specially crafted Microsoft Office file for the victim to open; the underlying mechanism is an out-of-bounds read in Office.

If you're affected

  • Confidential documents leaked
  • Customer or employee data exposure
  • Risk of account and business fraud
  • Incident response and downtime costs

Exploitation

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

EPSS43rd
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.5% chance of exploitation activity in the next 30 days, which ranks it in the 43rd 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. Publishedweakness classified, att&ck mapped, record updated, 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