CVE-2022-21826: Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the applic

Q: How do I fix CVE-2022-21826?

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

Q: Is CVE-2022-21826 being exploited?

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

Q: What does CVE-2022-21826 affect?

CVE-2022-21826 affects connect secure, pulse connect secure. Severity is medium (CVSS 5.4). Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This

Q: How urgent is CVE-2022-21826?

Priority 44/100. EPSS top 1%: very likely to be exploited

This week

MEDIUM 5.4DOWNGRADEUPGRADE

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

Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This body ends up prefixing the next HTTP request sent down that connection, this means when someone loads website attacker may be able to make browser issue a POST to the application, enabling XSS.

Why this priority

EPSS top 1%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	46.0% (top 1%)
CISA exploited list	No
Weakness	CWE-444
Published	2022-09-30
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: ivanti · pulsesecure

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

Am I affected?

Timeline

2022-09-30 17:15 UTCPublished CVE record published
2026-06-17 04:27 UTCUpdated Record last modified

ivanti connect secure DOWNGRADE

Affected: 9.1 · 9.1 r1 · 9.1 r1.0 · 9.1 r10.0 · 9.1 r10.2 · 9.1 r11.0 · 9.1 r11.1 · 9.1 r11.3

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-2022-21826?

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-2022-21826 being exploited?

CVE-2022-21826 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-2022-21826 affect?

CVE-2022-21826 affects connect secure, pulse connect secure. Severity is medium (CVSS 5.4). Pulse Secure version 9.115 and below may be susceptible to client-side http request smuggling, When the application receives a POST request, it ignores the request's Content-Length header and leaves the POST body on the TCP/TLS socket. This

How urgent is CVE-2022-21826?

Priority 44/100. EPSS top 1%: very likely to be exploited

Software pages

Ivanti vulnerabilities

Related CVEs

CVE-2026-111357 HIGH 7.0 EXPLOITED MITIGATE Ivanti Connect Secure Missing Authentication for Critical Function Vulnerability
CVE-2025-55141 HIGH 8.8 UPGRADE UPGRADE Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6
CVE-2025-55142 HIGH 8.8 UPGRADE UPGRADE Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6
CVE-2025-55145 HIGH 8.9 UPGRADE UPGRADE Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6
CVE-2025-55147 HIGH 8.8 UPGRADE UPGRADE CSRF in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6, Ivanti ZTA Gate

References

← Back to latest CVEs