# Project 2016 vulnerabilities

> Project 2016 is made by Microsoft. We track 2 published vulnerabilities in it, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 13 August 2024. If you run Project 2016, check your version against the exploited flaws below and patch those first.

Canonical page: https://www.precursorintelligence.com/product/microsoft/project_2016

## At a glance

- **Made by:** [Microsoft](https://www.precursorintelligence.com/vendors/microsoft)
- **Published vulnerabilities:** 2
- **Known to be exploited:** 1
- **Versions tracked:** 0
- **Most recently added to the known-exploited list:** [CVE-2024-38189](https://www.precursorintelligence.com/what-is/cve-2024-38189), 13 August 2024. We keep watching the list.

## Which versions of Project 2016 do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published. "before 16.0.5461.1001" means every version up to, but not including, 16.0.5461.1001.

- [CVE-2024-38189](https://www.precursorintelligence.com/what-is/cve-2024-38189) (Microsoft Project Remote Code Execution Vulnerability): before 16.0.5461.1001

## Which Project 2016 vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited, newest first:

- [CVE-2024-38189](https://www.precursorintelligence.com/what-is/cve-2024-38189): Microsoft Project Remote Code Execution Vulnerability. High, CVSS 8.8, chance of use in 30 days 8.2%, known exploited since 13 August 2024.

## Which Project 2016 flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast (the chance each flaw is used in an attack in the next 30 days):

- [CVE-2024-38189](https://www.precursorintelligence.com/what-is/cve-2024-38189): 8.2%, High (CVSS 8.8), known exploited
- [CVE-2020-1449](https://www.precursorintelligence.com/what-is/cve-2020-1449): 4.6%, High (CVSS 7.8)

## Questions

### How many vulnerabilities does Project 2016 have?

We track 2 published vulnerabilities listed under the name Project 2016, across 0 versions. The most recent Project 2016 flaw added to the known-exploited list is CVE-2024-38189, on 13 August 2024.

### Which Project 2016 vulnerabilities are being exploited?

1 is on the list of flaws known to be exploited. The most recently added is CVE-2024-38189.

### Which versions of Project 2016 do the exploited flaws affect?

Each flaw names its own versions, usually as ranges. The newest, CVE-2024-38189, affects before 16.0.5461.1001. The versions for every exploited flaw are listed on this page.

### How do I get alerts for Project 2016?

Create a Precursor Intelligence account and track Project 2016. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.

## Running Project 2016?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact