How severe is CVE-2017-6663?

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

Which products are affected by CVE-2017-6663?

CVE-2017-6663 affects the following products: cisco ios, cisco ios xe.

How do I patch CVE-2017-6663?

No patch has shipped for CVE-2017-6663 yet — track the cisco ios advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2017-6663 across my infrastructure?

Inventory every cisco ios deployment and check each version against the affected-products list above.

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

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

Yes. There are 2 known exploit references for CVE-2017-6663, including 2 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-6663?

CVE-2017-6663 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Yes. CVE-2017-6663 (Cisco IOS Software and Cisco IOS XE Software Denial-of-Service Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-03-24. 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.

Which products and versions are affected by CVE-2017-6663?

CVE-2017-6663 affects cisco ios (117 versions, e.g. 15.2\(3\)e, 15.2\(3\)e1, 15.2\(3\)e2…); cisco ios xe (69 versions, e.g. 3.7.0e, 3.7.1e, 3.7.3e…). Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2017-6663 was published on August 7, 2017 and was last updated on June 17, 2026. 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-6663 — IOS

MEDIUM

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

A vulnerability in the Autonomic Networking feature of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, adjacent attacker to cause autonomic nodes of an…

Published

Aug 7, 2017

Updated

Jun 17, 2026

Affected

2 products

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 23, 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-03-03. Federal agencies were required to remediate by 2022-03-24.

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

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2017-6663 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% band (highlighted). Counts from FIRST.org, log-scaled.

Description

A vulnerability in the Autonomic Networking feature of Cisco IOS Software and Cisco IOS XE Software could allow an unauthenticated, adjacent attacker to cause autonomic nodes of an affected system to reload, resulting in a denial of service (DoS) condition. More Information: CSCvd88936. Known Affected Releases: Denali-16.2.1 Denali-16.3.1.

Affected Products

2 products · 186 configurations

ioscisco

117 versions

15.2\(3\)e15.2\(3\)e115.2\(3\)e215.2\(3\)e315.2\(3\)e415.2\(3\)e515.2\(3a\)e15.2\(3a\)e115.2\(3m\)e215.2\(3m\)e315.2\(3m\)e615.2\(3m\)e8

ios xecisco

69 versions

3.7.0e3.7.1e3.7.3e3.8.0e3.8.0ex3.8.1e3.8.2e3.8.3e3.9.0e3.9.1e3.10.4s3.10.8as

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.

A vulnerability in the Autonomic Networking feature of Cisco IOS Softwar…

cisa.govAPIMar 2022

A vulnerability in the Autonomic Networking feature of Cisco IOS Softwar…

cisa.govCISAMar 2022

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every cisco ios deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2017-6663 yet — track the cisco ios advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2017-6663 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works