Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, an…

published 2015-05-13 11y ago modified 2026-06-17 4mo ago also EUVD-2015-1829

cvss: 9.3; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 14.1%; EPSS 14.1% chance of exploitation in 30 days, percentile 96%
public exploits: 0; none known

Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allow remote attackers to execute arbitrary code via a crafted Journal file, aka "Windows Journal Remote Code Execution Vulnerability," a different vulnerability than CVE-2015-1675, CVE-2015-1695, CVE-2015-1696, CVE-2015-1697, and CVE-2015-1698.

Patch / fix

links 1

docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-045 advisory

Is CVE-2015-1699 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 Fencer

Exploit prediction

14.12% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2015/ms15-045
vendor-advisory, patch
securitytracker.com /id/1032280
vdb-entry, third-party-advisory

Sources

CVE List CVE-2015-1699
NVD CVE-2015-1699

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.