How severe is CVE-2017-0022?

CVE-2017-0022 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-0022?

Affected package information for CVE-2017-0022 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-0022?

No fixed release is recorded for CVE-2017-0022 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2017-0022 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2017-0022 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is CVE-2017-0022 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2017-0022, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-0022?

CVE-2017-0022 has an EPSS (Exploit Prediction Scoring System) score of 18.1%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2017-0022 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-0022 (Microsoft XML Core Services Information Disclosure Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-24. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-14. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-0022?

CVE-2017-0022 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2017-0022 published, and has it been updated?

CVE-2017-0022 was published on March 17, 2017 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

MEDIUM severity

CVE-2017-0022 — Microsoft

MEDIUM

CVE-2017-0022 is a medium-severity (CVSS 6.5) Buffer Overflow vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-05-24) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; Windows 7 SP1; Windows 8.1; Windows RT 8.1; Windows Server 2008 SP2 and R2 SP1; Windows Server 2012 Gold and…

Published

Mar 17, 2017

Updated

Oct 21, 2025

Affected

4 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-05-24. Federal agencies were required to remediate by 2022-06-14.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-0022.

EPSS Exploitation Probability

via FIRST.org ↗

18.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-0022 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; Windows 7 SP1; Windows 8.1; Windows RT 8.1; Windows Server 2008 SP2 and R2 SP1; Windows Server 2012 Gold and R2; Windows Server 2016; and Windows Vista SP2 improperly handles objects in memory, allowing attackers to test for files on disk via a crafted web site, aka "Microsoft XML Information Disclosure Vulnerability."

Affected Products

4 products · 5 configurations

windows 8.1microsoft

all

windows server 2008microsoft

1 version

windows server 2012microsoft

1 version

Application

xml core servicesmicrosoft

1 version

3.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; …

portal.msrc.microsoft.comMSApr 2017

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; …

docs.microsoft.comGoogle-sheetMar 2017

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; …

cisa.govCISAMay 2022

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; …

0patch.blogspot.comNVDJul 2024

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2017-0022 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-0022 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-119Buffer Overflow

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Mar 17, 2017

First exploit

Apr 14, 2017

KEV added

May 24, 2022

Last updated

Oct 21, 2025

Identifiers

CVE-2017-0022

References

Websecurityfocus.com Web0patch.blogspot.com Webportal.msrc.microsoft.com Websecuritytracker.com Webcisa.gov

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-119 are rated as high or higher (top: high).

GHSA-qwgh-2vcv-g2f7CVE-2026-54559CVE-2022-46292CVE-2022-46293CVE-2025-10997CVE-2022-43467CVE-2022-46295CVE-2022-46291Browse all CWE-119

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 21, 2025

CVE-2017-0022 — Microsoft

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2017-0022 in your dependencies?