How severe is CVE-2018-0154?

CVE-2018-0154 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-0154?

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

How do I fix CVE-2018-0154?

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

How do I detect CVE-2018-0154 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-2018-0154 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.

Is CVE-2018-0154 actively exploited in the wild?

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

CVE-2018-0154 has an EPSS (Exploit Prediction Scoring System) score of 7.1%, placing it in the 94th 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-2018-0154 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-0154 (Cisco IOS Software Integrated Services Module for VPN 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-17. 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-2018-0154?

CVE-2018-0154 is classified as CWE-399 (CWE-399). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-0154 published, and has it been updated?

CVE-2018-0154 was published on March 28, 2018 and was last updated on January 12, 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

HIGH severity

CVE-2018-0154

HIGH

CVE-2018-0154 is a high-severity (CVSS 7.5) CWE-399 vulnerability. 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 crypto engine of the Cisco Integrated Services Module for VPN (ISM-VPN) running Cisco IOS Software could allow an unauthenticated, remote attacker to cause a…

Published

Mar 28, 2018

Updated

Jan 12, 2026

Affected

1 product

Patched

See advisory

Exploits

2 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-03-03. Federal agencies were required to remediate by 2022-03-17.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2018-0154.

EPSS Exploitation Probability

via FIRST.org ↗

7.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2018-0154 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 crypto engine of the Cisco Integrated Services Module for VPN (ISM-VPN) running Cisco IOS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to insufficient handling of VPN traffic by the affected device. An attacker could exploit this vulnerability by sending crafted VPN traffic to an affected device. A successful exploit could allow the attacker to cause the affected device to hang or crash, resulting in a DoS condition. Cisco Bug IDs: CSCvd39267.

Affected Products

1 product · 1 configurations

ioscisco

all

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 crypto engine of the Cisco Integrated Services Mo…

cisa.govAPIMar 2022

A vulnerability in the crypto engine of the Cisco Integrated Services Mo…

cisa.govCISAMar 2022

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-2018-0154 yet. Track the upstream advisory, and apply the exposure-reduction steps 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-0154 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works