# What is CVE-2019-15752?

> CVE-2019-15752 is a high-severity flaw (CVSS 7.8) in Docker, published on 28 August 2019. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 49%. If you run an affected version, patch it first.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2019-15752

## At a glance

- **Verdict:** Fix this now. Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
- **Precursor Intelligence risk score:** 74 out of 100 (High); action: Emergency patch. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 7.8 out of 10)
- **Known to be exploited:** Yes, it is on the government list of flaws known to be exploited
- **Chance of use in the next 30 days:** 49% (latest exploit-likelihood forecast)
- **Published:** 28 August 2019
- **Record last updated:** 14 March 2025
- **Main product:** Docker
- **Affected products:** 3

## What is CVE-2019-15752? In plain terms

An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

### The official description

Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by placing a Trojan horse docker-credential-wincred.exe file in %PROGRAMDATA%\DockerDesktop\version-bin\ as a low-privilege user, and then waiting for an admin or service user to authenticate with Docker, restart Docker, or run 'docker login' to force the command.

### What kind of flaw is it?

- CWE-732: Incorrect Permission Assignment for Critical Resource

### How an attack on it works

- Where an attacker can be: Already on the device
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: Yes, a person has to take an action
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`

## Is CVE-2019-15752 being exploited? Yes

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 49%.

Exploit likelihood over the last 7 days: 49%, 49%, 49%, 49%, 49%, 49%, 49%.

### Timeline

- 28 August 2019: Published
- 14 March 2025: Record last updated
- 3 September 2025: Exploit likelihood fell
- 22 November 2025: Exploit likelihood jumped

### How Precursor Intelligence ranks it

CVE-2019-15752 scores **74 out of 100 (High)**, with the action "Emergency patch".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2019-15752?

The published record lists 3 products. Versions are as published: "before 2.1.0.1" means every version up to, but not including, 2.1.0.1.

- [Docker](https://www.precursorintelligence.com/product/docker/docker) by [Docker](https://www.precursorintelligence.com/vendors/docker) (Application): before 2.1.0.1
- [Geode](https://www.precursorintelligence.com/product/apache/geode) by [Apache](https://www.precursorintelligence.com/vendors/apache) (Application): 1.12.0
- [Windows](https://www.precursorintelligence.com/product/microsoft/windows) by [Microsoft](https://www.precursorintelligence.com/vendors/microsoft) (Operating system): version not specified

## How do I fix CVE-2019-15752?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Check it wasn’t used before you patched.** Because criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.

### References

- [packetstormsecurity.com](http://packetstormsecurity.com/files/157404/Docker-Credential-Wincred.exe-Privilege-Escalation.html) (Exploit, Third-party advisory, Vulnerability database)
- [lists.apache.org](https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2%40%3Cissues.geode.apache.org%3E) (Mailing list)
- [medium.com](https://medium.com/%40morgan.henry.roman/elevation-of-privilege-in-docker-for-windows-2fd8450b478e) (Exploit, Third-party advisory)

## Questions

### What is CVE-2019-15752?

CVE-2019-15752 is a high-severity flaw in Docker, published on 28 August 2019. An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2019-15752?

It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2019-15752 is 74 out of 100, which is High. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.

### Is CVE-2019-15752 being exploited?

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 49%.

### Which versions does CVE-2019-15752 affect?

For Docker: before 2.1.0.1. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2019-15752?

Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.

## Does CVE-2019-15752 affect you?

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