CVE-2019-0618 in the critical feed json
A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory, aka…
published 7y ago modified 4mo ago also EUVD-2019-1382
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 67.0%
- EPSS 67.0% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 0
- none known
Summary
A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory, aka 'GDI+ Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0662.
Patch / fix
Is CVE-2019-0618 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
67.01% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Windows
- Microsoft Windows Server
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2019-0618
patch, vendor-advisory
-
securityfocus.com
/bid/106878
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-0618
- NVD CVE-2019-0618
Fencer Intel 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.