Skip to main content
VulnerabilityPublished Updated

CVE-2024-55225: vaultwarden · Incorrect Default Permissions

Affects vaultwardenSource CVE Database V5

0

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% 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:N/S:U/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

To mitigate CVE-2024-55225, organizations should immediately upgrade Vaultwarden to version 1.32.5 or later, where the vulnerability has been patched. If immediate patching is not feasible, restrict network access to Vaultwarden instances by implementing strict firewall rules and limiting exposure to trusted IP addresses only. Enable and review detailed logging of authorization requests to detect anomalous or suspicious activity indicative of exploitation attempts. Employ network segmentation to isolate Vaultwarden servers from critical infrastructure and sensitive data stores. Conduct regular audits of user accounts and permissions to identify unauthorized changes or suspicious privilege escalations. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to block malformed authorization requests targeting the identity API. Educate administrators and users about the risks and signs of compromise related to this vulnerability. Finally, maintain an incident response plan tailored to credential management system breaches to enable rapid containment and recovery.

Description

An issue in the component src/api/identity.rs of Vaultwarden prior to v1.32.5 allows attackers to impersonate users, including Administrators, via a crafted authorization request.

References

Community reviews

Loading reviews…