CVE-2022-36736: Jitsi-2.10.5550 was discovered to contain a vulnerability in its web UI which allows attackers to perform a cl
CVE-2022-36736 is a medium-severity flaw (CVSS 6.1) affecting jitsi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Jitsi-2.10.5550 was discovered to contain a vulnerability in its web UI which allows attackers to perform a clickjacking attack via a crafted HTTP request. NOTE: this is disputed by the vendor
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.7% (top 47%) |
| CISA exploited list | No |
| Weakness | CWE-1021 |
| Published | 2022-09-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-36736?
jitsi: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2022-36736 being exploited?
CVE-2022-36736 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-36736 affect?
CVE-2022-36736 affects jitsi. Severity is medium (CVSS 6.1). Jitsi-2.10.5550 was discovered to contain a vulnerability in its web UI which allows attackers to perform a clickjacking attack via a crafted HTTP request. NOTE: this is disputed by the vendor
How urgent is CVE-2022-36736?
Priority 35/100. No elevated risk signals yet.
Related CVEs
- CVE-2022-43550 CRITICAL 9.8 UPGRADE A command injection vulnerability exists in Jitsi before commit 8aa7be58522f4264078d54752aae5483bfd854b2 when