CVE-2022-21826

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

46.0% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-09-30 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:27 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 46.0% in the next 30 days (EPSS).
• Severity: 5.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-09-30 17:15 UTC

Last modified

2026-06-17 04:27 UTC

Exploit probability

46.0% · EPSS, next 30 days

Weakness

CWE-444

Record status

Modified

Affected

• Ivanti Connect Secure 9.1
• Pulsesecure Pulse Connect Secure < 9.1

Attack profile CVSS 3.1 · 5.4

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-21826.md and follow it. Check whether this project is affected by CVE-2022-21826. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge