CVE-2024-55226: vaultwarden · Cross-site Scripting
Affects vaultwardenSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Jan 2025
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdani-garcia/vaultwardenpkg:github/dani-garcia/vaultwardenOther 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-55226, organizations should first monitor Vaultwarden’s official channels for patches and apply updates as soon as they become available. In the interim, administrators should enforce strict access controls to limit authenticated user privileges, minimizing the potential attacker base. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. Educate users about phishing risks and the dangers of clicking on suspicious links, as user interaction is required for exploitation. Conduct regular security audits and penetration testing focusing on input validation and output encoding in the affected API endpoints. Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block reflected XSS payloads targeting Vaultwarden. Additionally, review and harden session management practices to limit the damage from stolen session tokens. Finally, isolate Vaultwarden instances in secure network segments and monitor logs for unusual activity indicative of attempted exploitation.
Description
Vaultwarden v1.32.5 was discovered to contain an authenticated reflected cross-site scripting (XSS) vulnerability via the component /api/core/mod.rs.