CVE-2024-38189: Microsoft Project Remote Code Execution
Microsoft Project · listed in the CISA catalog of actively exploited vulnerabilities since 2024-08-13.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 8.2%
- higher than 95% of all CVEs
- Added to CISA KEV
- 2024-08-13
- US federal due date 2024-09-03
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2024-38189 explained
CVE-2024-38189 is a remote code execution vulnerability in Microsoft Project, caused by improper input validation (CWE-20). Opening a malicious file can let an attacker run code. CISA lists it as known exploited, so attackers are actively using it.
Impact
An attacker who gets a user to open a malicious file can execute code with high impact on confidentiality, integrity and availability. No privileges are needed, but user interaction is required. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so each attack needs a user step. The vulnerability is known to be exploited. Ransomware use is unknown.
Who is affected
The CVE record lists Microsoft Project 2016 (32-bit and x64) before 16.0.5461.1001 as affected, fixed in 16.0.5461.1001. Microsoft Office 2019, Microsoft 365 Apps for Enterprise and Microsoft Office LTSC 2021 (32-bit and x64) are affected in builds before the fixed release, as stated in the vendor release notes. For these three products, the CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Project contains an unspecified vulnerability that allows for remote code execution via a malicious file.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Office 201932-bit, x64
- Microsoft 365 Apps for Enterprise32-bit, x64
- Microsoft Project 201632-bit, x64AffectedFixed in
- < 16.0.5461.1001
- 16.0.5461.1001
- Microsoft Office LTSC 202132-bit, x64
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Office 201932-bit, x64 |
| vendor release notes |
| Microsoft 365 Apps for Enterprise32-bit, x64 |
| vendor release notes |
| Microsoft Project 201632-bit, x64 |
|
|
| Microsoft Office LTSC 202132-bit, x64 |
| vendor release notes |
How to fix it
- Update to the fixed version for your product:
- Microsoft Project 2016: 16.0.5461.1001
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38189
- CISA's deadline for US federal agencies: 2024-09-03 (passed) – a useful benchmark for everyone else, too.
What to do
- Update Microsoft Project 2016 to
16.0.5461.1001or later. - Update Microsoft Office 2019, Microsoft 365 Apps for Enterprise and Microsoft Office LTSC 2021 to the fixed build listed in the vendor advisory and release notes.
- Apply mitigations per Microsoft's instructions, as CISA requires, or discontinue use if mitigations are unavailable.
- Warn users not to open Project files from untrusted or unexpected sources.
- Check systems for signs of compromise, since the vulnerability is known to be exploited.
For Microsoft Office 2019, Microsoft 365 Apps for Enterprise and Microsoft Office LTSC 2021, the CVE record names no fixed version. Check the Microsoft advisory and release notes for the fixed build. Follow CISA's required action: apply mitigations per vendor instructions, or discontinue use of the product if mitigations are unavailable. Until then, restrict the opening of untrusted Project files.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-20 Improper Input Validation
Questions about CVE-2024-38189
- Is CVE-2024-38189 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-08-13, with a US federal due date of 2024-09-03. Whether it is used in ransomware campaigns is unknown.
- Can it be exploited without user action?
- No. A user must open a malicious file. No privileges are required, and CISA rates it as not automatable.
- Which version fixes Microsoft Project 2016?
- Version
16.0.5461.1001. For the Office 2019, Microsoft 365 Apps for Enterprise and Office LTSC 2021 products, check the vendor release notes for the fixed build.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.