CVE-2026-27803: Vaultwarden Vaultwarden's Collection Management Operations Allowed Vulnerability

HIGH
Advisory Identifier: GHSA-h4hq-rgvh-wh27
CVSS 8.3
CWE-269 CWE-285 CWE-863
Published
Advisory Summary

CVE-2026-27803 is a HIGH (CVSS 8.3) vaultwarden's collection management operations allowed vulnerability (CWE-269: Improper Privilege Management) affecting Vaultwarden libraries in the crates.io ecosystem. The issue involves vaultwarden's collection management operations allowed without `manage` verification for manager role. Remediation is available by upgrading affected packages to version 1.35.4.

CVE-2026-27803 at a Glance

CVE Identifier CVE-2026-27803
GHSA Identifier GHSA-h4hq-rgvh-wh27
Severity HIGH
CVSS v3.1 Base Score 8.3
CWE Classification CWE-269: Improper Privilege Management
Affected Product Vaultwarden
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 8.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-27803

To remediate this vulnerability, upgrade all affected Vaultwarden dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

vaultwarden fixed: 1.35.4
Upgrade vaultwarden to 1.35.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for vaultwarden

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-27803, inspect your project dependencies for Vaultwarden:

inspect dependencies for vaultwarden

Analyze the terminal output to locate any version of Vaultwarden in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.35.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In Vaultwarden, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Testing confirmed that even when a Manager has `manage=false` for a given collection, they can still perform the following management operations as long as they have access to the collection: * `PUT /api/organizations/<org_id>/collections/<col_id>` succeeds (HTTP 200) * `PUT /api/organizations/<org_id>/collections/<col_id>/users` succeeds (HTTP 200) * `DELETE /api/organizations/<org_id>/collections/<col_id>` succeeds (HTTP 200) ## Description * The Manager guard checks only whether the user **can access the collection**, not whether they have `manage` privileges. This check is directly applied to management endpoints. src/auth.rs:816 ```rust if !Collection::can_access_collection(&headers.membership, &col_id, &conn).await { err_handler!("The current user isn't a manager for this collection") } ``` * The `can_access_collection` function does **not** evaluate the `manage` flag. src/db/models/collection.rs:140 ```rust pub async fn can_access_collection(member: &Membership, col_id: &CollectionId, conn: &DbConn) -> bool { member.has_status(MembershipStatus::Confirmed) && (member.has_full_access() || CollectionUser::has_access_to_collection_by_user(col_id, &member.user_uuid, conn).await || ... ``` * A separate management-permission check exists and includes `manage` validation, but it is **not used** during authorization for the affected endpoints. src/db/models/collection.rs:516 ```rust pub async fn is_manageable_by_user(&self, user_uuid: &UserId, conn: &DbConn) -> bool { let Some(member) = Membership::find_confirmed_by_user_and_org(user_uuid, &self.org_uuid, conn).await else { return false; }; if member.has_full_access() { return true; } ... ``` * The actual update and deletion endpoints only accept `ManagerHeaders` and do not perform additional `manage` checks. src/api/core/organizations.rs:608 ```rust async fn put_organization_collection_update(..., headers: ManagerHeaders, ...) ``` src/api/core/organizations.rs:890 ```rust async fn put_collection_users(..., headers: ManagerHeaders, ...) ``` src/api/core/organizations.rs:747 ```rust async fn delete_organization_collection(..., headers: ManagerHeaders, ...) ``` ## Preconditions * The attacker is a **Manager** within the target organization. * The attacker has access to the target collection (`assigned=true`). * The attacker’s permission for that collection is `manage=false`. * A valid API access token has been obtained. ## Steps to Reproduce 1. Confirm that the attacker’s current permissions for the target collection include `manage=false`. <img width="2015" height="636" alt="image" src="https://github.com/user-attachments/assets/58ddc733-e37c-4766-a980-b1ea1918ceb4" /> 2. As a control test, verify that update operations fail for collections the attacker cannot access. <img width="2021" height="852" alt="image" src="https://github.com/user-attachments/assets/d8699442-2dfc-4d73-8940-ec10f4a175f0" /> 3. Confirm that update operations succeed for the target collection where `manage=false`. <img width="2013" height="690" alt="image" src="https://github.com/user-attachments/assets/33d9845d-d18e-456c-a58c-e780911347a9" /> 4. Use `PUT /collections/{col_id}/users` to set `manage=true`, confirming that the attacker can escalate their own privileges. <img width="2018" height="488" alt="image" src="https://github.com/user-attachments/assets/da8c5246-cf2a-46c2-9a25-e99d907f852d" /> 5. Verify that deletion of the collection succeeds despite the Manager lacking management rights. <img width="2018" height="487" alt="image" src="https://github.com/user-attachments/assets/a97c8fb2-4f97-4c2a-a90b-9d95dbde84fd" /> ## Required Minimum Privileges * Organization Manager role (Owner/Admin privileges are not required) * Works even with `access_all=false` * Only access rights to the target collection are required (`manage` privilege is not required) ## Attack Scenario A restricted Manager (intended for read/use-only access) directly invokes the API to update collection settings, elevate their own privileges to `manage=true`, and even delete the collection. This allows the user to bypass operational access restrictions and effectively gain administrator-equivalent control over the collection. ## Potential Impact * **Confidentiality:** Expansion of access scope through unauthorized privilege escalation and configuration changes. * **Integrity:** Unauthorized modification of collection settings and assignments; potential disabling of access controls. * **Availability:** Deletion of collections may disrupt business operations.

CVE-2026-27803 Affected Vaultwarden Versions

1 component(s)
Fixed Versions:
1.35.4
Product / Package Ecosystem Affected Versions Fixed Version
vaultwarden
crates.io
< 1.35.4
1.35.4

References

Frequently Asked Questions

What is CVE-2026-27803?
CVE-2026-27803 is a security vulnerability in Vaultwarden involving Vaultwarden's Collection Management Operations Allowed Without `manage` Verification for Manager Role under CWE-269: Improper Privilege Management.
Which Vaultwarden versions are affected?
Affected versions include releases prior to 1.35.4 across affected packages: vaultwarden.
What version fixes CVE-2026-27803?
Upgrading to 1.35.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is vaultwarden affected?
Yes, vaultwarden is affected in releases prior to 1.35.4. Upgrade your dependency to 1.35.4 or later.
What is the CVSS score of CVE-2026-27803?
CVE-2026-27803 has a CVSS v3.1 base score of 8.3 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with CVE-2026-27803?
CVE-2026-27803 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check crates.io dependencies for CVE-2026-27803?
Run the dependency tree command: 'inspect dependencies for vaultwarden'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h4hq-rgvh-wh27",
  "modified" : "2026-03-04T20:13:44Z",
  "published" : "2026-03-04T20:13:44Z",
  "aliases" : [ "CVE-2026-27803" ],
  "summary" : "Vaultwarden's Collection Management Operations Allowed Without `manage` Verification for Manager Role",
  "details" : "## Summary\n\nTesting confirmed that even when a Manager has `manage=false` for a given collection, they can still perform the following management operations as long as they have access to the collection:\n\n* `PUT /api/organizations/<org_id>/collections/<col_id>` succeeds (HTTP 200)\n* `PUT /api/organizations/<org_id>/collections/<col_id>/users` succeeds (HTTP 200)\n* `DELETE /api/organizations/<org_id>/collections/<col_id>` succeeds (HTTP 200)\n\n\n\n## Description\n\n* The Manager guard checks only whether the user **can access the collection**, not whether they have `manage` privileges. This check is directly applied to management endpoints.\nsrc/auth.rs:816\n  ```rust\n\n  if !Collection::can_access_collection(&headers.membership, &col_id, &conn).await {\n      err_handler!(\"The current user isn't a manager for this collection\")\n  }\n  ```\n\n* The `can_access_collection` function does **not** evaluate the `manage` flag.\n  src/db/models/collection.rs:140\n\n  ```rust\n\n  pub async fn can_access_collection(member: &Membership, col_id: &CollectionId, conn: &DbConn) -> bool {\n      member.has_status(MembershipStatus::Confirmed)\n          && (member.has_full_access()\n              || CollectionUser::has_access_to_collection_by_user(col_id, &member.user_uuid, conn).await\n              || ...\n  ```\n\n* A separate management-permission check exists and includes `manage` validation, but it is **not used** during authorization for the affected endpoints.\n  src/db/models/collection.rs:516\n\n  ```rust\n\n  pub async fn is_manageable_by_user(&self, user_uuid: &UserId, conn: &DbConn) -> bool {\n      let Some(member) = Membership::find_confirmed_by_user_and_org(user_uuid, &self.org_uuid, conn).await else {\n          return false;\n      };\n      if member.has_full_access() {\n          return true;\n      }\n      ...\n  ```\n\n* The actual update and deletion endpoints only accept `ManagerHeaders` and do not perform additional `manage` checks.\n  src/api/core/organizations.rs:608\n\n```rust\n  async fn put_organization_collection_update(..., headers: ManagerHeaders, ...)\n```\n\n  src/api/core/organizations.rs:890\n\n```rust\n  async fn put_collection_users(..., headers: ManagerHeaders, ...)\n```\n  \n\nsrc/api/core/organizations.rs:747\n\n```rust\n  async fn delete_organization_collection(..., headers: ManagerHeaders, ...)\n  ```\n\n\n\n## Preconditions\n\n* The attacker is a **Manager** within the target organization.\n* The attacker has access to the target collection (`assigned=true`).\n* The attacker’s permission for that collection is `manage=false`.\n* A valid API access token has been obtained.\n\n\n\n## Steps to Reproduce\n\n1. Confirm that the attacker’s current permissions for the target collection include `manage=false`.\n<img width=\"2015\" height=\"636\" alt=\"image\" src=\"https://github.com/user-attachments/assets/58ddc733-e37c-4766-a980-b1ea1918ceb4\" />\n\n2. As a control test, verify that update operations fail for collections the attacker cannot access.\n<img width=\"2021\" height=\"852\" alt=\"image\" src=\"https://github.com/user-attachments/assets/d8699442-2dfc-4d73-8940-ec10f4a175f0\" />\n\n3. Confirm that update operations succeed for the target collection where `manage=false`.\n<img width=\"2013\" height=\"690\" alt=\"image\" src=\"https://github.com/user-attachments/assets/33d9845d-d18e-456c-a58c-e780911347a9\" />\n\n4. Use `PUT /collections/{col_id}/users` to set `manage=true`, confirming that the attacker can escalate their own privileges.\n<img width=\"2018\" height=\"488\" alt=\"image\" src=\"https://github.com/user-attachments/assets/da8c5246-cf2a-46c2-9a25-e99d907f852d\" />\n\n5. Verify that deletion of the collection succeeds despite the Manager lacking management rights.\n<img width=\"2018\" height=\"487\" alt=\"image\" src=\"https://github.com/user-attachments/assets/a97c8fb2-4f97-4c2a-a90b-9d95dbde84fd\" />\n\n\n\n## Required Minimum Privileges\n\n* Organization Manager role (Owner/Admin privileges are not required)\n* Works even with `access_all=false`\n* Only access rights to the target collection are required (`manage` privilege is not required)\n\n\n\n## Attack Scenario\n\nA restricted Manager (intended for read/use-only access) directly invokes the API to update collection settings, elevate their own privileges to `manage=true`, and even delete the collection.\n\nThis allows the user to bypass operational access restrictions and effectively gain administrator-equivalent control over the collection.\n\n\n\n## Potential Impact\n\n* **Confidentiality:** Expansion of access scope through unauthorized privilege escalation and configuration changes.\n* **Integrity:** Unauthorized modification of collection settings and assignments; potential disabling of access controls.\n* **Availability:** Deletion of collections may disrupt business operations.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "vaultwarden"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.35.4"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.35.3"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-h4hq-rgvh-wh27"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dani-garcia/vaultwarden"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269", "CWE-285", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-04T20:13:44Z",
    "nvd_published_at" : null
  }
}