CVE-2026-27803
Privilege Escalation in Vaultwarden Collection Management Pre
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-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
| 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?
The vulnerability exists in Vaultwarden, an unofficial Bitwarden compatible server. Before version 1.35.4, a user with Manager role but with manage=false permission for a specific collection could still perform several management operations on that collection if they had access to it. This means the intended restriction on management capabilities was bypassed.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized management actions on collections by users who should not have such permissions. As a result, sensitive data could be altered, deleted, or otherwise mismanaged, potentially compromising confidentiality, integrity, and availability of the data stored in Vaultwarden.
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 vulnerability, you should upgrade Vaultwarden to version 1.35.4 or later, where the issue has been patched.