CVE-2026-27802
Privilege Escalation in Vaultwarden via Bulk Permission Update
Publication date: 2026-03-04
Last updated on: 2026-03-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dani-garcia | vaultwarden | to 1.35.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Vaultwarden, an unofficial Bitwarden compatible server. Before version 1.35.4, a user with Manager privileges could escalate their privileges by performing a bulk permission update on collections they are not authorized to access. This means that a Manager could gain unauthorized access or control over collections they should not have permission to manage.
How can this vulnerability impact me? :
The vulnerability allows a user with Manager privileges to escalate their access rights improperly, potentially gaining unauthorized access to sensitive collections. This can lead to exposure, modification, or deletion of confidential data stored within those collections, compromising confidentiality, integrity, and availability.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this privilege escalation vulnerability in Vaultwarden, you should upgrade your Vaultwarden server to version 1.35.4 or later, where the issue has been patched.