Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2021-22937: A vulnerability in Pulse Connect Secure before 9.1R12 could allow an authenticated administrator to perform a

49
This month
HIGH 7.2DOWNGRADEUPGRADE

CVE-2021-22937 is a high-severity flaw (CVSS 7.2) affecting connect secure, pulse connect secure. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability in Pulse Connect Secure before 9.1R12 could allow an authenticated administrator to perform a file write via a maliciously crafted archive uploaded in the administrator web interface.

Why this priority

  • High severity
  • EPSS top 5%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score7.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance7.8% (top 5%)
CISA exploited listNo
WeaknessCWE-434
Published2021-08-16
Last modified2026-06-17
Publisher (CNA): HackerOne · Vendor: ivanti · pulsesecure

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

ivanti connect secure DOWNGRADE
Affected: 9.1 · 9.1 r1.0 · 9.1 r10.0 · 9.1 r11.0 · 9.1 r2.0 · 9.1 r3.0 · 9.1 r4.0 · 9.1 r5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.1
1. Check installed version
apt-cache policy connect-secure || rpm -q connect-secure || connect-secure --version
2. No fixed release: DOWNGRADE to a release before 9.1 (Debian / Ubuntu)
apt-cache madison connect-secure sudo apt install connect-secure=<VERSION_BEFORE_9.1> sudo apt-mark hold connect-secure
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list connect-secure sudo dnf downgrade connect-secure-<VERSION_BEFORE_9.1> sudo dnf versionlock add connect-secure
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
pulsesecure pulse connect secure UPGRADE
Affected: < 9.1
Fixed in: 9.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy pulse-connect-secure || rpm -q pulse-connect-secure || pulse-connect-secure --version
2. UPGRADE to 9.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade pulse-connect-secure
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade pulse-connect-secure
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-22937?

connect secure: downgrade or apply the listed mitigation; pulse connect secure: upgrade to 9.1. Exact commands for each OS are on this page.

Is CVE-2021-22937 being exploited?

CVE-2021-22937 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-22937 affect?

CVE-2021-22937 affects connect secure, pulse connect secure. Severity is high (CVSS 7.2). A vulnerability in Pulse Connect Secure before 9.1R12 could allow an authenticated administrator to perform a file write via a maliciously crafted archive uploaded in the administrator web interface.

How urgent is CVE-2021-22937?

Priority 49/100. High severity; EPSS top 5%: very likely to be exploited

Software pages

Ivanti vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.