Skip to content
skopnix

CVE-2020-8218 · Published 30 Jul 2020

Pulse Secure Pulse Connect Secure

On CISA's KEV list 585 days after disclosure; 1 public exploit.

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

CISA required action (federal due date 7 Sep 2022): Apply updates per vendor instructions.

Signals

KEV, exploited in the wild
yes, added 7 Mar 2022, due 7 Sep 2022
EPSS, 30-day forecast
32%, 98th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 30 Jul 2020 to today

585 days from disclosure to the KEV listing
2023202420252026Disclosed 30 Jul 2020KEV 7 Mar 2022today
  1. Disclosed
  2. KEV+585 d

585 days from disclosure to the KEV listing

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code 1 known · links only

GitHub PoCs 1Metasploit 0Exploit-DB 0

GitHub PoCs, by trust then stars1

  1. first seen by skopnix 18 Oct 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check