How severe is CVE-2020-8218?

CVE-2020-8218 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-8218?

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

How do I fix CVE-2020-8218?

No fixed version has been published for CVE-2020-8218 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2020-8218 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2020-8218, including 5 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-2020-8218?

CVE-2020-8218 has an EPSS (Exploit Prediction Scoring System) score of 91.1%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2020-8218 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-8218 (Pulse Connect Secure Code Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-07. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-09-07. 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-2020-8218?

CVE-2020-8218 is classified as Code Injection (CWE-94). 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.

Which products and versions are affected by CVE-2020-8218?

CVE-2020-8218 affects ivanti connect secure (1 version, e.g. 9.1); ivanti policy secure (1 version, e.g. 9.1); pulsesecure pulse policy secure. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2020-8218 published, and has it been updated?

CVE-2020-8218 was published on July 30, 2020 and was last updated on October 30, 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·Added 2022-03-07 — agencies required to remediate by 2022-09-07

CVE-2020-8218

HIGH

A code injection vulnerability exists in Pulse Connect Secure <9.1R8 that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.

Published

Jul 30, 2020

Updated

Oct 30, 2025

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

91.1%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A code injection vulnerability exists in Pulse Connect Secure <9.1R8 that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.

Affected Products

3 products · 24 configurations

Application

connect secureivanti

≤ 9.0

1 version

9.1

Application

policy secureivanti

1 version

9.1

Application

pulse policy securepulsesecure

≤ 9.0

range

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.