Summary
Vaultwarden contained an authorization flaw where users with access to a collection could perform certain management actions even when their Manager role for that collection was explicitly set to manage=false.
Under these conditions, a non-manager could overstep intended permissions and modify shared resources, undermining Vaultwarden's collection-based access control model.
Affected context
The vulnerability appears in Vaultwarden deployments using role- or permission-based access control for collections, where a user is assigned a Manager role but with the manage flag disabled for a specific collection.
In these scenarios, the system still allowed some management operations to succeed as long as the user retained access to the collection itself.
Environments with multiple shared collections, delegated management, or fine-grained role configurations are more likely to be affected, especially where owners rely on manage=false to restrict administrative actions.
Exploit preconditions
- Attack surface: Vaultwarden web/UI and API operations involving collection and item management.
- Required access: Authenticated Vaultwarden account with access to at least one collection where:
- The user is a Manager (or similar role) for the organization or collection, and
- The manage=false setting is intended to block management capabilities on that collection.
- Trigger point: Performing management-like actions (e.g., modifying aspects of a collection or its contents) via the application interface or API that should be blocked when manage=false is set.
- Why exploitation is possible: The server-side authorization logic ties effective permissions too closely to collection access and role identity, and does not consistently re-check the manage flag for all relevant operations. As a result, certain management operations bypass the intended permission boundary.
Why this happens
This issue stems from incomplete or inconsistent enforcement of authorization checks for collection management operations.
Instead of deriving permissions solely from the explicit manage flag and collection-specific constraints, some code paths rely on broader indicators such as general collection access or role membership, allowing actions that should require manage=true.
This behavior maps to:
- CWE-285: Improper Authorization, where the application fails to enforce intended access control rules.
- CWE-269: Improper Privilege Management, due to the system granting a more powerful set of capabilities than the configured role specifies.
- CWE-863: Incorrect Authorization, because the server-side logic incorrectly infers that access to a collection implies authorization to perform certain management operations.
Potential impact
- Non-manager users may be able to perform certain management operations on collections that should be restricted.
- Users with limited delegated rights could modify shared collection data or configuration beyond what owners intended.
- Organizational access boundaries within Vaultwarden may be weakened, undermining the security model for shared vaults.
- In multi-tenant or tightly controlled environments, this could contribute to broader data governance or compliance issues.
General mitigation guidance
Mitigation generally focuses on tightening and centralizing authorization logic for all collection-related operations:
- Ensure that every management operation on collections and their metadata performs a server-side check that explicitly verifies the manage flag for the current user and collection.
- Use a clear, centralized permission model where effective rights are derived from a single source of truth (e.g., a permission matrix) rather than scattered conditional checks.
- Design roles and flags so that default behavior is restrictive (deny-by-default) and additional privileges are explicitly granted.
- Limit the number of roles with any management capabilities, and require explicit elevation for management tasks to reduce accidental over-privilege.
- Document intended permission behavior for collections and ensure that implementation and tests align with this model.
How teams detect issues like this
High-level detection and assurance approaches include:
- Code-level review:
- Identify all endpoints and methods that alter collection properties, membership, or related administrative data.
- Verify that each path enforces checks on both collection access and the manage flag (or equivalent fine-grained permission).
- Look for authorization logic implemented in controllers or handlers instead of a central authorization layer.
- Static analysis and automated checks:
- Configure static analysis or linters to flag direct state-changing operations on collections that are not preceded by calls to standardized authorization helpers.
- Use policy-as-code or security linters to enforce a deny-by-default pattern for sensitive operations.
- Behavioral and audit logging:
- Log management actions with user ID, role, collection ID, and effective permissions used to authorize the request.
- Periodically review logs for management actions coming from accounts that should not have full management rights.

