CVE-2024-38189

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Microsoft Project. For every flaw being used in attacks, see Exploited flaws; for Microsoft’s, see Microsoft flaws being used in attacks.

CVE-2024-38189 is a security flaw in Microsoft Project. Opening a booby-trapped file can let an attacker run their own code through Microsoft Project. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 13 Aug 2024.[1]

Microsoft Project is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed in version https://aka.ms/OfficeSecurityReleases and 16.0.5461.1001.

Description

CISA calls it a remote code execution in Microsoft Project. In its words: “Microsoft Project contains an unspecified vulnerability that allows for remote code execution via a malicious file.”[1]

The underlying weakness is improper input validation (CWE-20), in MITRE’s list of common software weaknesses.[2]

It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]

ProductFixed in
Microsoft Office 2019https://aka.ms/OfficeSecurityReleases
Microsoft 365 Apps for Enterprisehttps://aka.ms/OfficeSecurityReleases
Microsoft Project 201616.0.5461.1001
Microsoft Office LTSC 2021https://aka.ms/OfficeSecurityReleases

Most families won’t have Microsoft Project; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 13 Aug 2024, within a day of it being made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 3 Sep 2024 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 8%. That’s in the top 6% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Microsoft has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Microsoft Project is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed (fixed in version https://aka.ms/OfficeSecurityReleases and 16.0.5461.1001), or not in use. CISA gave US government agencies until 3 Sep 2024 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 8%.[4]

See also

Other Microsoft flaws

  • CVE-2026-96951, Microsoft Windows: command injection ·
  • CVE-2026-65660, Microsoft SharePoint: code injection ·
  • CVE-2026-85880, Microsoft Windows: heap-based buffer overflow ·
  • CVE-2026-81963, Microsoft Windows: link following ·
  • CVE-2019-1068, Microsoft SQL Server: remote code execution ·

Other improper input validation flaws

  • CVE-2026-93952, Arista VeloCloud Orchestrator: improper input validation ·
  • CVE-2026-12569, PTC Windchill and FlexPLM: improper input validation ·
  • CVE-2026-34910, Ubiquiti UniFi OS: improper input validation ·
  • CVE-2026-6973, Ivanti Endpoint Manager Mobile (EPMM): improper input validation ·
  • CVE-2026-34197, Apache ActiveMQ: improper input validation ·

Added the same day

  • CVE-2024-38213, Microsoft Windows: smartScreen security feature bypass ·
  • CVE-2024-38193, Microsoft Windows: ancillary function driver for winSock privilege escalation ·
  • CVE-2024-38178, Microsoft Windows: scripting engine memory corruption ·
  • CVE-2024-38107, Microsoft Windows: power dependency coordinator privilege escalation ·
  • CVE-2024-38106, Microsoft Windows: kernel privilege escalation ·

Every Microsoft flaw on CISA’s list · Everything added in August 2024

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Microsoft Project Remote Code Execution Vulnerability”. Known Exploited Vulnerabilities Catalog, added 13 Aug 2024.
  2. ^ National Institute of Standards and Technology. “CVE-2024-38189 Detail”. National Vulnerability Database, published 13 Aug 2024.
  3. ^ Microsoft. Advisories and fixes: msrc.microsoft.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.082, percentile 94.9, 31 Oct 2026.
  5. CVE Program. “CVE-2024-38189”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.