# What is CVE-2022-21826? > CVE-2022-21826 is a medium-severity flaw (CVSS 5.4) in Connect Secure from Ivanti, published on 30 September 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 45%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-21826 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 38 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 5.4 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 45% (latest exploit-likelihood forecast) - **Published:** 30 September 2022 - **Record last updated:** 27 February 2024 - **Main product:** Connect Secure from Ivanti - **Affected products:** 2 ## What is CVE-2022-21826? In plain terms It can be attacked from anywhere on the internet with an ordinary user account, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### The official description 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. ### What kind of flaw is it? - CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: An ordinary user account - Does someone have to click: Yes, a person has to take an action - What an attacker gets: Can read some data and change some data Severity vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N` ## Is CVE-2022-21826 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 45%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 45%, 45%, 45%, 45%, 45%, 45%, 45%. ### Timeline - 30 September 2022: Published - 27 February 2024: Record last updated - 8 October 2025: Exploit likelihood fell - 16 June 2026: Exploit likelihood jumped ### How Precursor Intelligence ranks it CVE-2022-21826 scores **38 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2022-21826? The published record lists 2 products. Versions are as published: "before 9.1" means every version up to, but not including, 9.1. - [Connect Secure](https://www.precursorintelligence.com/product/ivanti/connect_secure) by [Ivanti](https://www.precursorintelligence.com/vendors/ivanti) (Application): 9.1, 9.1-r1, 9.1-r1.0, 9.1-r2, 9.1-r2.0, 9.1-r3, 9.1-r3.0, 9.1-r4, 9.1-r4.0, 9.1-r4.1, 9.1-r4.2, 9.1-r4.3, 9.1-r5, 9.1-r5.0, 9.1-r6, 9.1-r6.0, 9.1-r7, 9.1-r7.0, 9.1-r8, 9.1-r8.0, 9.1-r8.1, 9.1-r8.2, 9.1-r8.4, 9.1-r9, 9.1-r9.0, 9.1-r9.1, 9.1-r9.2, 9.1-r10.0, 9.1-r10.2, 9.1-r11.0, 9.1-r11.1, 9.1-r11.3, 9.1-r11.4, 9.1-r12, 9.1-r12.1, 9.1-r12.2, 9.1-r13, 9.1-r15 - [Pulse Connect Secure](https://www.precursorintelligence.com/product/pulsesecure/pulse_connect_secure) by [Pulsesecure](https://www.precursorintelligence.com/vendors/pulsesecure) (Application): before 9.1 ## How do I fix CVE-2022-21826? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [kb.pulsesecure.net](https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/Client-Side-Desync-Attack/) (Vendor advisory) ## Questions ### What is CVE-2022-21826? CVE-2022-21826 is a medium-severity flaw in Connect Secure from Ivanti, published on 30 September 2022. It can be attacked from anywhere on the internet with an ordinary user account, but a person has to take an action first. If it works, the attacker can read some data and change some data. ### How serious is CVE-2022-21826? It scores 5.4 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-21826 is 38 out of 100, which is Low. Its action is "Monitor". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2022-21826 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 45%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2022-21826 affect? For Connect Secure from Ivanti: 9.1, 9.1-r1, 9.1-r1.0, 9.1-r2, 9.1-r2.0, 9.1-r3 and 32 more. The record lists 2 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2022-21826? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2022-21826 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact