How severe is GHSA-x7m9-mv49-fv73?

No CVSS score has been assigned to GHSA-x7m9-mv49-fv73 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x7m9-mv49-fv73?

GHSA-x7m9-mv49-fv73 affects the following packages: vaultwarden (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-x7m9-mv49-fv73?

Update vaultwarden to 1.32.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7m9-mv49-fv73 is resolved across your whole dependency graph.

How do I detect GHSA-x7m9-mv49-fv73 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vaultwarden, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x7m9-mv49-fv73 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is GHSA-x7m9-mv49-fv73 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x7m9-mv49-fv73 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x7m9-mv49-fv73?

GHSA-x7m9-mv49-fv73 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-x7m9-mv49-fv73?

GHSA-x7m9-mv49-fv73 is classified as Incorrect Default Permissions (CWE-276). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x7m9-mv49-fv73 published, and has it been updated?

GHSA-x7m9-mv49-fv73 was published on January 9, 2025 and was last updated on January 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Vaultwarden vulnerable to user impersonationGHSA-x7m9-mv49-fv73

Fix: dani-garcia/vaultwarden@20d9e88

GHSA-x7m9-mv49-fv73 is a Incorrect Default Permissions vulnerability in vaultwarden. A fix is available for vaultwarden — see the affected versions and patch details below.

Also known asCVE-2024-55225

Published

Jan 9, 2025

Updated

Jan 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-x7m9-mv49-fv73.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀vaultwarden

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`vaultwarden`	all versions	1.32.5`cargo update -p vaultwarden --precise 1.32.5`

Affected Products

1 product · 1 configurations

Application

vaultwardendani-garcia

< 1.32.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vaultwarden, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vaultwarden to 1.32.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x7m9-mv49-fv73 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-x7m9-mv49-fv73 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works