Microsoft Project Remote Code Execution Vulnerability

cisa required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

1. 2024-08-13 0-day patched (Project Zero)
2. 2024-08-13 Added to CISA KEV
3. 2024-08-13 Published
4. 2024-08-14 CISA SSVC: exploitation active
5. 2024-09-03 CISA patch deadline

Added

2 y ago (2024-08-13)

Patch by

2024-09-03 (2 y ago)

Ransomware

Not known

Required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Vendor, product

Microsoft, Project

CISA name

Microsoft Project Remote Code Execution Vulnerability

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Patched

2024-08-13

Details

project zero tracker

Exploitation

Active, exploited in the wild

Automatable

no

Technical impact

total

Assessed

2 y ago (2024-08-14)

8.19% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).

• Microsoft Microsoft Office 2019
• Microsoft Microsoft 365 Apps for Enterprise
• Microsoft Microsoft Project 2016
• Microsoft Microsoft Office LTSC 2021

Weakness

• CWE-20 Improper Input Validation

• msrc.microsoft.com /update-guide/vulnerability/CVE-2024-38189

  vendor-advisory, patch

• cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38189

  government-resource, us-government-resource

• CVE List CVE-2024-38189
• NVD CVE-2024-38189

Fencer Vulns 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.