Skip to content
skopnix

CVE-2020-8260 · Published 28 Oct 2020

Ivanti Pulse Connect Secure

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

Pulse Connect Secure contains an unspecified vulnerability that allows an authenticated attacker to perform code execution using uncontrolled gzip extraction.

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

Signals

KEV, exploited in the wild
yes, added 3 Nov 2021, due 3 May 2022
EPSS, 30-day forecast
96%, 100th 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 28 Oct 2020 to today

331 days from the Metasploit module to the KEV listing
2023202420252026Disclosed 28 Oct 2020Metasploit 7 Dec 2020KEV 3 Nov 2021today
  1. Disclosed
  2. Metasploit+40 d
  3. KEV+331 d

331 days from the Metasploit module 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 0Metasploit 1Exploit-DB 0

Metasploit1

  1. The Pulse Connect Secure appliance before 9.1R9 suffers from an uncontrolled gzip extraction vulnerability which allows an attacker to overwrite arbitrary files, resulting in Remote Code Execution as root. Admin credentials are required for successful exploitation. Of note, MANY binaries are not in `$PATH`, but are located in `/home/bin/`.

    ruby · first seen by skopnix 18 Oct 2026

References

Watch this one?

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

Telegram ↗KEV RSSAPIStack check