dbcve.org
VaultwardenApplication · Dani Garcia

CVE-2024-39925

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in Vaultwarden (formerly Bitwarden_RS) 1.30.3. It lacks an offboarding process for members who leave an organization. As a result, the shared organization key is not rotated when a member departs. Consequently, the departing member, whose access should be revoked, retains a copy of the organization key. Additionally, the application fails to adequately protect some encrypted data stored on the server. Consequently, an authenticated user could gain unauthorized access to encrypted data of any organization, even if the user is not a member of the targeted organization. However, the user would need to know the corresponding organizationId. Hence, if a user (whose access to an organization has been revoked) already possesses the organization key, that user could use the key to decrypt the leaked data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vaultwarden 1.30.3 lacks a member offboarding process - when members leave an organization, the shared organization encryption key is not rotated, allowing former members to retain the key. Additionally, the application inadequately protects encrypted data, enabling any authenticated user who knows an organizationId to access that organization's encrypted data without proper authorization.

MitigationImplement proper member offboarding that rotates organization keys upon departure and add access controls to prevent unauthorized access to encrypted organization data regardless of whether the user knows the organizationId.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VaultwardenApplication
Affected:= 1.30.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Vaultwarden version
    Check the running Vaultwarden instance version (typically via /admin diagnostics page, API endpoint, or container image tag)
    Affected if The installed version is exactly 1.30.3
  2. Verify member offboarding key rotation
    Review Vaultwarden source code or configuration for any function that rotates the organization's symmetric encryption key when a member is removed from an organization
    Affected if No key rotation logic exists or is triggered upon member removal
  3. Check organization data access controls
    Test whether an authenticated user from one organization can access another organization's encrypted data by directly querying with a known organizationId (via API or internal function calls)
    Affected if Users can access encrypted data belonging to organizations they are not a member of by supplying the organizationId

You are affected if running Vaultwarden 1.30.3 AND your organization lacks proper member offboarding with key rotation OR allows unauthorized access to encrypted organization data based on knowledge of organizationId.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper member offboarding that rotates organization keys upon departure and add access controls to prevent unauthorized access to encrypted organization data regardless of whether the user knows the organizationId.

Recommended fix High confidence

Vaultwarden 1.30.4 or later

  1. 1. Backup your current Vaultwarden instance and database before upgrading
  2. 2. Stop the Vaultwarden service
  3. 3. Update Vaultwarden to version 1.30.4 or later
  4. 4. Restart the Vaultwarden service
  5. 5. Verify the service is running correctly
  6. 6. Test that user offboarding now properly handles organization key rotation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vaultwarden Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39925 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data