CVE-2015-1701 — Microsoft Win32k Privilege Escalation Vulnerability

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

• Documented patch — docs.microsoft.com (NIST National Vulnerability Database)

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Mar 24, 2022 — passed 1666 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 2003 Server, Microsoft Windows 7, Microsoft Windows Server 2008…).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. Apply the fixed version or the patch documented under Remediation.
4. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

Threat actors exploiting this CVE MITRE ATT&CK

According to MITRE ATT&CK.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 55.92%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
• Hunt retroactively in logs from before Mar 3, 2022 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Fix documented
  Oct 13, 2026 · NIST National Vulnerability Database
• Affected products added · microsoft/windows 2003 server, microsoft/windows 7, microsoft/windows server 2008, microsoft/windows vista
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 7.8
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• 2022
• Added to CISA KEV catalog
  Mar 2, 2022 · CISA
• 2015
• CVE published
  Apr 21, 2015 · microsoft

Source activity

Repeated readings are counted rather than listed.

• 2× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

13 on the record

• docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-051
  Patch, Vendor Advisory, vendor-advisory, x_refsource_MS, NIST National Vulnerability Database
• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• seclists.org/fulldisclosure/2020/May/34
  Broken Link, Mailing List, Third Party Advisory, mailing-list, x_refsource_FULLDISC, NIST National Vulnerability Database
• www.exploit-db.com/exploits/37049/
  Exploit, Third Party Advisory, VDB Entry, exploit, x_refsource_EXPLOIT-DB, NIST National Vulnerability Database
• www.exploit-db.com/exploits/37367/
  Exploit, Third Party Advisory, VDB Entry, exploit, x_refsource_EXPLOIT-DB, NIST National Vulnerability Database
• www.fireeye.com/blog/threat-research/2015/04/probable_apt28_useo.html
  Third Party Advisory, x_refsource_MISC, NIST National Vulnerability Database
• www.exploit-db.com/exploits/37367
  GitHub Security Advisories
• www.securitytracker.com/id/1032155
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
• twitter.com/symantec/statuses/590208710527549440
  Press/Media Coverage, x_refsource_MISC, NIST National Vulnerability Database
• www.exploit-db.com/exploits/37049
  GitHub Security Advisories
• github.com/advisories/GHSA-rq9p-fw9r-ppg4
  GitHub Security Advisories
• www.securityfocus.com/bid/74245
  Broken Link, Third Party Advisory, VDB Entry, vdb-entry, x_refsource_BID, NIST National Vulnerability Database
• nvd.nist.gov/vuln/detail/CVE-2015-1701
  GitHub Security Advisories

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-20940 Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability Jan 13, 2026
• High CVE-2026-20931 Windows Telephony Service Elevation of Privilege Vulnerability Jan 13, 2026
• Medium CVE-2026-20936 Windows NDIS Information Disclosure Vulnerability Jan 13, 2026
• High CVE-2026-20929 Windows HTTP.sys Elevation of Privilege Vulnerability Jan 13, 2026
• Medium CVE-2026-20925 NTLM Hash Disclosure Spoofing Vulnerability Jan 13, 2026
• Medium CVE-2026-20927 Windows SMB Server Denial of Service Vulnerability Jan 13, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No CWE classification.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2015-1701 is "Microsoft Win32k Privilege Escalation Vulnerability", rated High. It affects Windows 2003 Server (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 55.92% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.