CVE-2024-44081: jitsi-meet · Cross-site Scripting
Affects jitsi-meetSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.0.9779 as a priority.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.9779
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade jitsi/jitsi-meet to 2.0.9779.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjitsi/jitsi-meetpkg:github/jitsi/jitsi-meetOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-44081, organizations should immediately upgrade Jitsi Meet to version 2.0.9779 or later where the vulnerability is fixed. If you cannot patch yet, network administrators should implement strict filtering of outbound and inbound URLs in conferencing traffic to block untrusted or suspicious domains. Employ Content Security Policy (CSP) headers and input validation mechanisms to restrict loading of external resources in the client application. Disable or restrict the video file sharing feature if possible to reduce attack surface. Monitor conferencing sessions for unusual activity or messages containing suspicious URLs. Educate users about the risk of interacting with untrusted participants or links during meetings. Additionally, consider deploying endpoint protection solutions that can detect and block script-based attacks originating from conferencing clients. Regularly review and audit conferencing platform configurations and logs to identify potential exploitation attempts. Collaborate with Jitsi community or vendor support channels for timely updates and security advisories.
Description
In Jitsi Meet before 2.0.9779, the functionality to share a video file was implemented in an insecure way, resulting in clients loading videos from an arbitrary URL if a message from another participant contains a URL encoded in the expected format.