vaultwarden
Affected
- introduced
0, fixed1.35.4(semver)
Fixed versions
1.35.4
Fix
- Fixed version
1.35.4cargo update -p vaultwarden --precise 1.35.4
Advisory
Also known as: CVE-2026-27802
Vaultwarden has Privilege Escalation via Bulk Permission Update to Unauthorized Collections by Manager
Summary
A Manager account (access_all=false) was able to escalate privileges by directly invoking the bulk-access API against collections that were not originally assigned to them.
The API allowed changing assigned=false to assigned=true, resulting in unauthorized access.
Additionally, prior to the bulk-access call, the regular single-update API correctly returned 401 Unauthorized for the same collection. After executing the bulk-access API, the same update API returned 200 OK, confirming an authorization gap at the HTTP level.
---
Description
ManagerHeadersLoose and does not validate access rights for the specified collectionIds. src/api/core/organizations.rs:551 headers: ManagerHeadersLoose,
collection_ids are processed directly without per-collection authorization checks. src/api/core/organizations.rs:564 for col_id in data.collection_ids {
CollectionGroup::delete_all_by_collection(&col_id, &conn).await?;
CollectionUser::delete_all_by_collection(&col_id, &conn).await?;
from_loose. src/api/core/organizations.rs:787 let headers = ManagerHeaders::from_loose(headers, &collections, &conn).await?;
can_access_collection, which is not invoked in the bulk-access endpoint. src/auth.rs:911 if !Collection::can_access_collection(&h.membership, col_id, conn).await {
---
Preconditions
---
Steps to Reproduce
<img width="4016" height="1690" alt="image" src="https://github.com/user-attachments/assets/218f05e2-6a2e-4066-8f8d-6bbef1cc5858" />
assigned, manage, readOnly, and hidePasswords for the target collection.<img width="4026" height="1694" alt="image" src="https://github.com/user-attachments/assets/a6d2fc70-5370-4984-85bd-a6f74febdfa3" />
<img width="4030" height="1708" alt="image" src="https://github.com/user-attachments/assets/802f0d2b-d474-44d2-beef-b4f7f3335225" />
<img width="4036" height="1120" alt="image" src="https://github.com/user-attachments/assets/1d3caa01-3ac2-4636-9ed0-189e5923c986" />
collectionIds containing the target collectionusers containing the attacker’s own membership_id Confirm that the API returns 200 OK.<img width="4040" height="1440" alt="image" src="https://github.com/user-attachments/assets/340e9676-d802-404c-b894-9986a176360a" />
---
Required Minimum Privileges
access_all=false)---
Attack Scenario
A delegated administrator or department-level Manager within an organization directly calls the API to add themselves to unauthorized collections and gain access to confidential information.
Because the bulk update process deletes and reassigns existing permissions, the attacker can also remove other users’ access, enabling denial-of-service or sabotage within the organization.
---
Potential Impact
High Basis: The source's own band: HIGH
0, fixed 1.35.4 (semver)1.35.4
1.35.4cargo update -p vaultwarden --precise 1.35.4Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0