CVE-2026-27802: Vaultwarden Vaultwarden Has Privilege Escalation Vulnerability

HIGH
Advisory Identifier: GHSA-r32r-j5jq-3w4m
CVSS 8.3
CWE-269 CWE-863
Published
Advisory Summary

CVE-2026-27802 is a HIGH (CVSS 8.3) vaultwarden has privilege escalation vulnerability (CWE-269: Improper Privilege Management) affecting Vaultwarden libraries in the crates.io ecosystem. The issue involves vaultwarden has privilege escalation via bulk permission update to unauthorized collections by manager. Remediation is available by upgrading affected packages to version 1.35.4.

CVE-2026-27802 at a Glance

CVE Identifier CVE-2026-27802
GHSA Identifier GHSA-r32r-j5jq-3w4m
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-27802

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-27802, 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 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 * The endpoint accepts `ManagerHeadersLoose` and does not validate access rights for the specified `collectionIds`. src/api/core/organizations.rs:551 ```rust headers: ManagerHeadersLoose, ``` * The received `collection_ids` are processed directly without per-collection authorization checks. src/api/core/organizations.rs:564 ```rust for col_id in data.collection_ids { ``` * Existing group assignments for the collection are deleted. src/api/core/organizations.rs:583 ```rust CollectionGroup::delete_all_by_collection(&col_id, &conn).await?; ``` * Existing user assignments for the collection are deleted. src/api/core/organizations.rs:590 ```rust CollectionUser::delete_all_by_collection(&col_id, &conn).await?; ``` * By comparison, another bulk-processing endpoint performs per-collection validation using `from_loose`. src/api/core/organizations.rs:787 ```rust let headers = ManagerHeaders::from_loose(headers, &collections, &conn).await?; ``` * The actual access control logic is implemented in `can_access_collection`, which is not invoked in the bulk-access endpoint. src/auth.rs:911 ```rust if !Collection::can_access_collection(&h.membership, col_id, conn).await { ``` --- ## Preconditions * The attacker possesses a valid **Manager account** within the target organization. * The organization contains collections that are **not assigned** to the attacker. * The attacker can authenticate through the standard API login process (Owner/Admin privileges are not required). --- ## Steps to Reproduce 1. Log in as a Manager and obtain a Bearer token. <img width="4016" height="1690" alt="image" src="https://github.com/user-attachments/assets/218f05e2-6a2e-4066-8f8d-6bbef1cc5858" /> 2. Confirm the current values of `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" /> 3. Verify that the standard update API returns **401 Unauthorized** when attempting to modify the unassigned collection. <img width="4030" height="1708" alt="image" src="https://github.com/user-attachments/assets/802f0d2b-d474-44d2-beef-b4f7f3335225" /> 4. Invoke the bulk-access API, including: <img width="4036" height="1120" alt="image" src="https://github.com/user-attachments/assets/1d3caa01-3ac2-4636-9ed0-189e5923c986" /> * `collectionIds` containing the target collection * `users` containing the attacker’s own `membership_id` Confirm that the API returns **200 OK**. 5. Re-run the standard update API. Confirm that it now succeeds and that the previously unauthorized modification is applied. <img width="4040" height="1440" alt="image" src="https://github.com/user-attachments/assets/340e9676-d802-404c-b894-9986a176360a" /> --- ## Required Minimum Privileges * Manager role within the target organization (the issue occurs even when `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 * **Confidentiality:** Unauthorized access to sensitive information within restricted collections. * **Integrity:** Unauthorized modification of collection permission settings and arbitrary changes to access controls. * **Availability:** Deletion of existing assignments may cause legitimate users to lose access.

CVE-2026-27802 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-27802?
CVE-2026-27802 is a security vulnerability in Vaultwarden involving Vaultwarden has Privilege Escalation via Bulk Permission Update to Unauthorized Collections by Manager 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-27802?
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-27802?
CVE-2026-27802 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-27802?
CVE-2026-27802 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-27802?
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-r32r-j5jq-3w4m",
  "modified" : "2026-03-04T20:07:21Z",
  "published" : "2026-03-04T20:07:21Z",
  "aliases" : [ "CVE-2026-27802" ],
  "summary" : "Vaultwarden has Privilege Escalation via Bulk Permission Update to Unauthorized Collections by Manager",
  "details" : "## Summary\n\nA 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.\nThe API allowed changing `assigned=false` to `assigned=true`, resulting in unauthorized access.\n\nAdditionally, 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.\n\n---\n\n## Description\n\n* The endpoint accepts `ManagerHeadersLoose` and does not validate access rights for the specified `collectionIds`.\n  src/api/core/organizations.rs:551\n\n  ```rust\n  headers: ManagerHeadersLoose,\n  ```\n\n* The received `collection_ids` are processed directly without per-collection authorization checks.\n  src/api/core/organizations.rs:564\n\n  ```rust\n  for col_id in data.collection_ids {\n  ```\n\n* Existing group assignments for the collection are deleted.\n  src/api/core/organizations.rs:583\n\n  ```rust\n  CollectionGroup::delete_all_by_collection(&col_id, &conn).await?;\n  ```\n\n* Existing user assignments for the collection are deleted.\n  src/api/core/organizations.rs:590\n\n  ```rust\n  CollectionUser::delete_all_by_collection(&col_id, &conn).await?;\n  ```\n\n* By comparison, another bulk-processing endpoint performs per-collection validation using `from_loose`.\n  src/api/core/organizations.rs:787\n\n  ```rust\n  let headers = ManagerHeaders::from_loose(headers, &collections, &conn).await?;\n  ```\n\n* The actual access control logic is implemented in `can_access_collection`, which is not invoked in the bulk-access endpoint.\n  src/auth.rs:911\n\n  ```rust\n  if !Collection::can_access_collection(&h.membership, col_id, conn).await {\n  ```\n\n---\n\n## Preconditions\n\n* The attacker possesses a valid **Manager account** within the target organization.\n* The organization contains collections that are **not assigned** to the attacker.\n* The attacker can authenticate through the standard API login process (Owner/Admin privileges are not required).\n\n---\n\n## Steps to Reproduce\n\n1. Log in as a Manager and obtain a Bearer token.\n<img width=\"4016\" height=\"1690\" alt=\"image\" src=\"https://github.com/user-attachments/assets/218f05e2-6a2e-4066-8f8d-6bbef1cc5858\" />\n\n2. Confirm the current values of `assigned`, `manage`, `readOnly`, and `hidePasswords` for the target collection.\n<img width=\"4026\" height=\"1694\" alt=\"image\" src=\"https://github.com/user-attachments/assets/a6d2fc70-5370-4984-85bd-a6f74febdfa3\" />\n\n3. Verify that the standard update API returns **401 Unauthorized** when attempting to modify the unassigned collection.\n<img width=\"4030\" height=\"1708\" alt=\"image\" src=\"https://github.com/user-attachments/assets/802f0d2b-d474-44d2-beef-b4f7f3335225\" />\n\n4. Invoke the bulk-access API, including:\n<img width=\"4036\" height=\"1120\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1d3caa01-3ac2-4636-9ed0-189e5923c986\" />\n\n   * `collectionIds` containing the target collection\n   * `users` containing the attacker’s own `membership_id`\n     Confirm that the API returns **200 OK**.\n\n5. Re-run the standard update API.\n   Confirm that it now succeeds and that the previously unauthorized modification is applied.\n<img width=\"4040\" height=\"1440\" alt=\"image\" src=\"https://github.com/user-attachments/assets/340e9676-d802-404c-b894-9986a176360a\" />\n\n---\n\n## Required Minimum Privileges\n\n* Manager role within the target organization\n  (the issue occurs even when `access_all=false`)\n\n---\n\n## Attack Scenario\n\nA 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.\n\nBecause 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.\n\n---\n\n## Potential Impact\n\n* **Confidentiality:** Unauthorized access to sensitive information within restricted collections.\n* **Integrity:** Unauthorized modification of collection permission settings and arbitrary changes to access controls.\n* **Availability:** Deletion of existing assignments may cause legitimate users to lose access.",
  "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-r32r-j5jq-3w4m"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/dani-garcia/vaultwarden"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-04T20:07:21Z",
    "nvd_published_at" : null
  }
}