cve.bz

CVE-2022-21826 HTTP Request Smuggling

5.4 mediumEPSS 46%

Medium (5.4). EPSS 46% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS
46% (unchanged from 46% a week ago; 46% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-21826 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-21826?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-21826?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-21826 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_secure9.1
ivanti:connect_secure9.1:r1
ivanti:connect_secure9.1:r1.0
ivanti:connect_secure9.1:r10.0
ivanti:connect_secure9.1:r10.2
ivanti:connect_secure9.1:r11.0
ivanti:connect_secure9.1:r11.1
ivanti:connect_secure9.1:r11.3
ivanti:connect_secure9.1:r11.4
ivanti:connect_secure9.1:r12
ivanti:connect_secure9.1:r12.1
ivanti:connect_secure9.1:r12.2
ivanti:connect_secure9.1:r13
ivanti:connect_secure9.1:r15
ivanti:connect_secure9.1:r2
ivanti:connect_secure9.1:r2.0
ivanti:connect_secure9.1:r3
ivanti:connect_secure9.1:r3.0
ivanti:connect_secure9.1:r4
ivanti:connect_secure9.1:r4.0
ivanti:connect_secure9.1:r4.1
ivanti:connect_secure9.1:r4.2
ivanti:connect_secure9.1:r4.3
ivanti:connect_secure9.1:r5
ivanti:connect_secure9.1:r5.0
ivanti:connect_secure9.1:r6
ivanti:connect_secure9.1:r6.0
ivanti:connect_secure9.1:r7
ivanti:connect_secure9.1:r7.0
ivanti:connect_secure9.1:r8
ivanti:connect_secure9.1:r8.0
ivanti:connect_secure9.1:r8.1
ivanti:connect_secure9.1:r8.2
ivanti:connect_secure9.1:r8.4
ivanti:connect_secure9.1:r9
ivanti:connect_secure9.1:r9.0
ivanti:connect_secure9.1:r9.1
ivanti:connect_secure9.1:r9.2
pulsesecure:pulse_connect_securebefore 9.1

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON