CVE-2026-27898: Vaultwarden Vaultwarden Has Unauthorized Access Vulnerability
MODERATECVE-2026-27898 is a MODERATE (CVSS 5.4) vaultwarden has unauthorized access vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Vaultwarden libraries in the crates.io ecosystem. The issue involves vaultwarden has unauthorized access via partial update api on another user’s cipher. Remediation is available by upgrading affected packages to version 1.35.4.
CVE-2026-27898 at a Glance
Security Impact
CVSS: 5.4
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:L/I:L/A:N).
How to Fix CVE-2026-27898
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.
Upgrade vaultwarden to 1.35.4
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-27898, 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-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. 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
CVE-2026-27898 Affected Vaultwarden Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
vaultwarden
|
crates.io |
< 1.35.4
|
1.35.4
|
References
Frequently Asked Questions
What is CVE-2026-27898?
Which Vaultwarden versions are affected?
What version fixes CVE-2026-27898?
Is vaultwarden affected?
What is the CVSS score of CVE-2026-27898?
What CWE is associated with CVE-2026-27898?
How can I check crates.io dependencies for CVE-2026-27898?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-w9f8-m526-h7fh",
"modified" : "2026-03-04T20:14:06Z",
"published" : "2026-03-04T20:14:06Z",
"aliases" : [ "CVE-2026-27898" ],
"summary" : "Vaultwarden has Unauthorized Access via Partial Update API on Another User’s Cipher",
"details" : "## Summary\n\nIn the test environment, it was confirmed that an authenticated regular user can specify another user’s `cipher_id` and call:\n\n```\nPUT /api/ciphers/{id}/partial\n```\n\nEven though the standard retrieval API correctly denies access to that cipher, the partial update endpoint returns **200 OK** and exposes `cipherDetails` (including `name`, `notes`, `data`, `secureNote`, etc.).\n\n\n\n## Description\n\n`put_cipher_partial` retrieves the target Cipher but does **not perform ownership or access control checks** before returning `to_json`.\nAuthorization checks present in the normal update API are missing here.\nsrc/api/core/ciphers.rs:717\n\n```rust\nlet Some(cipher) = Cipher::find_by_uuid(&cipher_id, &conn).await else {\n err!(\"Cipher doesn't exist\")\n};\n\nif let Some(ref folder_id) = data.folder_id {\n if Folder::find_by_uuid_and_user(folder_id, &headers.user.uuid, &conn).await.is_none() {\n err!(\"Invalid folder\", \"Folder does not exist or belongs to another user\");\n }\n}\n\n// Move cipher\ncipher.move_to_folder(data.folder_id.clone(), &headers.user.uuid, &conn).await?;\n\n// Update favorite\ncipher.set_favorite(Some(data.favorite), &headers.user.uuid, &conn).await?;\n\nOk(Json(cipher.to_json(&headers.host, &headers.user.uuid, None, CipherSyncType::User, &conn).await?))\n```\n\nBy comparison, the standard update API includes an explicit authorization check:\nsrc/api/core/ciphers.rs:688\n\n```rust\nif !cipher.is_write_accessible_to_user(&headers.user.uuid, &conn).await {\n err!(\"Cipher is not write accessible\")\n}\n```\n\nThe `to_json` method does not abort processing when access restrictions are not met; instead, it proceeds to construct and return a detailed response.\nsrc/db/models/cipher.rs:175\n\n```rust\nlet (read_only, hide_passwords, _) = if sync_type == CipherSyncType::User {\n match self.get_access_restrictions(user_uuid, cipher_sync_data, conn).await {\n Some((ro, hp, mn)) => (ro, hp, mn),\n None => {\n error!(\"Cipher ownership assertion failure\");\n (true, true, false)\n }\n }\n} else {\n (false, false, false)\n};\n```\nsrc/db/models/cipher.rs:335\n\n```rust\nlet mut json_object = json!({\n \"object\": \"cipherDetails\",\n \"id\": self.uuid,\n \"type\": self.atype,\n ...\n \"name\": self.name,\n \"notes\": self.notes,\n \"fields\": fields_json,\n \"data\": data_json,\n ...\n});\n```\n\n\n## Preconditions\n\n* The attacker possesses a valid regular-user JWT (Bearer token).\n* The attacker knows the target (victim) `cipher_id`.\n\n\n## Steps to Reproduce\n\n1. Prepare the attacker JWT and victim `cipher_id` (preconditions).\n2. Baseline check: confirm that standard retrieval is denied.\n<img width=\"2014\" height=\"855\" alt=\"image\" src=\"https://github.com/user-attachments/assets/32b12cc9-3672-4a88-afd0-ef7715474662\" />\n\n\n3. Execute the vulnerable API. Confirm that **200 OK** is returned and that `cipherDetails` includes fields such as `id`, `name`, `notes`, `secureNote`, etc.\n<img width=\"2018\" height=\"1113\" alt=\"image\" src=\"https://github.com/user-attachments/assets/341b330c-8d55-4f06-a622-0d7da28f62fd\" />\n\n\n## Potential Impact\n\n* Unauthorized disclosure of other users’ cipher information (confidentiality breach).\n* Creation of unauthorized associations within the attacker’s user context (e.g., `favorite` or folder operations).\n* The response from `/api/ciphers/<cipher_id>/partial` includes `attachments[].url`.\n\nIn filesystem (FS) deployments, this returns a tokenized endpoint such as:\n\n```\n/attachments/<cipher>/<file>?token=...\n```\n\nIn object storage deployments, it returns a short-lived pre-signed URL.\n\nAs a result, an attacker can use these URLs to directly download attachment data that they are not authorized to access.\n\nThis can lead to disclosure of sensitive information stored in the Vault, including personal data and authentication credentials. Such exposure may further result in account compromise, lateral movement, and other secondary impacts.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
} ],
"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-w9f8-m526-h7fh"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/dani-garcia/vaultwarden"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-639" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-04T20:14:06Z",
"nvd_published_at" : null
}
}