CVE-2026-27898
Insecure Direct Object Reference in Vaultwarden Cipher Update API
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-639 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Vaultwarden, an unofficial Bitwarden compatible server. Before version 1.35.4, an authenticated regular user could specify another user's cipher_id and use the "PUT /api/ciphers/{id}/partial" endpoint. Although the standard retrieval API correctly denies access to that cipher, this partial update endpoint incorrectly returns a 200 OK response and exposes sensitive cipher details such as name, notes, data, and secureNote.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive information stored in other users' ciphers. An attacker with authenticated access could view confidential data like names, notes, and secure notes of other users, potentially leading to privacy breaches and data leakage.
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.