Skip to main content
VulnerabilityPublished Updated

CVE-2024-55224: vaultwarden · An HTML Injection

Affects vaultwardenSource CVE Database V5

0

Not known to be exploited · CVSS 9.6 Critical : upgrade to 1.32.5 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.32.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 dani-garcia/vaultwarden to 1.32.5.

Affected software

ProductAffectedFixed in
GitHubdani-garcia/vaultwardenpkg:github/dani-garcia/vaultwardenOther threatsAffected
  • <1.32.5
Fixed in
  • 1.32.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Vaultwarden installations to version 1.32.5 or later, where this vulnerability is fixed. Until patching is possible, administrators should consider restricting access to Vaultwarden interfaces via network segmentation and firewall rules to limit exposure. Employing web application firewalls (WAFs) with rules to detect and block suspicious HTML or script injection attempts can provide temporary protection. Educate users to be cautious with unexpected or suspicious emails, especially those containing links or requests involving Vaultwarden credentials. Regularly audit and monitor Vaultwarden logs for unusual activity that could indicate exploitation attempts. Implement strict input validation and output encoding in any custom integrations with Vaultwarden to prevent injection flaws. Finally, maintain an incident response plan to quickly address potential breaches resulting from this vulnerability.

Description

An HTML injection vulnerability in Vaultwarden prior to v1.32.5 allows attackers to execute arbitrary code via injecting a crafted payload into the username field of an e-mail message.

References

Community reviews

Loading reviews…