vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2024-20677

Microsoft Office Remote Code Execution Vulnerability

HIGH
7.8
CVSS Score
Published: January 9, 2024 at 05:56 PM UTC
Updated: June 17, 2026 at 07:07 AM UTC
6 products affected across 1 vendorOffice365 AppsOffice Long Term Servicing Channel

Using 3D Viewer by Microsoft?

Get instant alerts when new vulnerabilities affect 3D Viewer - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.8
Exploit prediction
EPSS 3%
SSVC
No known exploit

Description

A security vulnerability exists in FBX that could lead to remote code execution. To mitigate this vulnerability, the ability to insert FBX files has been disabled in Word, Excel, PowerPoint and Outlook for Windows and Mac. Versions of Office that had this feature enabled will no longer have access to it. This includes Office 2019, Office 2021, Office LTSC for Mac 2021, and Microsoft 365. As of February 13, 2024, the ability to insert FBX files has also been disabled in 3D Viewer. 3D models in Office documents that were previously inserted from a FBX file will continue to work as expected unless the Link to File option was chosen at insert time. This change is effective as of the January 9, 2024 security update.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

365 Apps· Microsoft
95%
16.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.1
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
3D Viewer· Microsoft
95%
7.0.0 ≤ v < 7.2401.29012.07.0.0
Affected range stops below 7.2401.29012.0, so it looks safe — our inference, not a vendor statement
Office· Microsoft
95%
19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases2019
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
Office Long Term Servicing Channel· Microsoft
95%
16.0.1 ≤ v < 16.81.2401142016.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases2021
Affected range stops below 16.81.24011420, so it looks safe — our inference, not a vendor statement
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
Office 2019· Microsoft
60%
19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases19.0.0
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
Office 2021· Microsoft
60%
16.0.1 ≤ v < 16.81.2401142016.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.1
Affected range stops below 16.81.24011420, so it looks safe — our inference, not a vendor statement
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor AdvisoryPatch
Source: [email protected]
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-20677

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-122NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card