Skip to content
Fencer Intel
low 3.3

CVE-2026-45485 json

Microsoft Office Information Disclosure Vulnerability

published 5mo ago modified last mo. also EUVD-2026-35653

cvss
3.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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

Patch / fix

  • Microsoft Microsoft Office 2016 16.0.5556.1005
  • Microsoft Microsoft Office 365 for Mac 16.110.26061317
  • Microsoft Microsoft Office LTSC for Mac 2021 16.110.26061317
  • Microsoft Microsoft Office LTSC for Mac 2024 16.110.26061317
  • Microsoft Microsoft SharePoint Enterprise Server 2016 16.0.5556.1005
  • Microsoft Microsoft SharePoint Server 2019 16.0.10417.20153
  • Microsoft Microsoft SharePoint Server Subscription Edition 16.0.19725.20384

Is CVE-2026-45485 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:U/RL:O/RC:C
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Affected products

  • Microsoft Microsoft 365 Apps for Enterprise
  • Microsoft Microsoft Office 2016
  • Microsoft Microsoft Office 2019
  • Microsoft Microsoft Office 365 for Mac
  • Microsoft Microsoft Office LTSC 2021
  • Microsoft Microsoft Office LTSC 2024
  • Microsoft Microsoft Office LTSC for Mac 2021
  • Microsoft Microsoft Office LTSC for Mac 2024
  • Microsoft Microsoft SharePoint Enterprise Server 2016
  • Microsoft Microsoft SharePoint Server 2019
  • Microsoft Microsoft SharePoint Server Subscription Edition

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.