Compatibility Issue: Bitwarden CLI 2025.12.0 fails with "User Decryption Options are required" on older Vaultwarden versions #152

New Issue

MrUnknownDE · 2026-04-05T20:32:58+02:00

MrUnknownDE commented

2026-04-05 20:32:58 +02:00

Originally created by @SionS4R on 1/17/2026

Prerequisites

I have searched the existing Closed AND Open Issues AND Discussions
I have searched and read the documentation

Vaultwarden Support String

I encountered a breaking compatibility issue between the latest Bitwarden CLI (version 2025.12.0) and Vaultwarden server (version 1.35.2).

Attempts to login or unlock the vault using bw login --apikey fail with the error:
Error: User Decryption Options are required for client initialization. userDecryptionOptions is missing in response.

This appears to be caused by changes in the official Bitwarden CLI v2025.12.0 expecting KDF/decryption fields that older Vaultwarden versions do not return during the API key authentication flow.

Workaround
Downgrading the Bitwarden CLI to version 2025.11.0 resolves the issue immediately.

1 npm install -g @bitwarden/cli@2025.11.0

Server Environment

Vaultwarden Version: 1.35.2
Install Method: Docker

Client Environment

Bitwarden CLI Version: 2025.12.0
OS: Linux (Ubuntu)

Note: I am opening this issue to alert other users and maintainers about this client-side breaking change that affects existing Vaultwarden installations.

Vaultwarden Build Version

1.35.2

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

npm v2.13.6

Host/Server Operating System

Linux

Operating System Version

No response

Clients

CLI

Client Version

No response

Steps To Reproduce

Run Vaultwarden Server version 1.35.2.
Install Bitwarden CLI version 2025.12.0 (npm install -g @bitwarden/cli@2025.12.0).
Configure the server: bw config server .
Attempt login using API Key:

1 export BW_CLIENTID="user.xxxxx"
2 export BW_CLIENTSECRET="yyyyy"
3 bw login --apikey

Expected Result

The CLI should authenticate successfully and allow vault unlock, as it did in previous versions.

Actual Result

The command fails with:

1 Error: User Decryption Options are required for client initialization. userDecryptionOptions is missing in response.
Manual login via email/password also fails with Username or password is incorrect due to protocol mismatches.

Logs

Screenshots or Videos

No response

Additional Context

No response

*Originally created by @SionS4R on 1/17/2026* ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String I encountered a breaking compatibility issue between the latest Bitwarden CLI (version 2025.12.0) and Vaultwarden server (version 1.35.2). Attempts to login or unlock the vault using bw login --apikey fail with the error: Error: User Decryption Options are required for client initialization. userDecryptionOptions is missing in response. This appears to be caused by changes in the official Bitwarden CLI v2025.12.0 expecting KDF/decryption fields that older Vaultwarden versions do not return during the API key authentication flow. Workaround Downgrading the Bitwarden CLI to version 2025.11.0 resolves the issue immediately. 1 npm install -g @bitwarden/cli@2025.11.0 Server Environment - Vaultwarden Version: 1.35.2 - Install Method: Docker Client Environment - Bitwarden CLI Version: 2025.12.0 - OS: Linux (Ubuntu) --- Note: I am opening this issue to alert other users and maintainers about this client-side breaking change that affects existing Vaultwarden installations. ### Vaultwarden Build Version 1.35.2 ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy npm v2.13.6 ### Host/Server Operating System Linux ### Operating System Version _No response_ ### Clients CLI ### Client Version _No response_ ### Steps To Reproduce 1. Run Vaultwarden Server version 1.35.2. 2. Install Bitwarden CLI version 2025.12.0 (npm install -g @bitwarden/cli@2025.12.0). 3. Configure the server: bw config server <your-vaultwarden-url>. 4. Attempt login using API Key: 1 export BW_CLIENTID="user.xxxxx" 2 export BW_CLIENTSECRET="yyyyy" 3 bw login --apikey ### Expected Result The CLI should authenticate successfully and allow vault unlock, as it did in previous versions. ### Actual Result The command fails with: 1 Error: User Decryption Options are required for client initialization. userDecryptionOptions is missing in response. Manual login via email/password also fails with Username or password is incorrect due to protocol mismatches. ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_

MrUnknownDE closed this issue

2026-04-05 20:32:58 +02:00

MrUnknownDE added the bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug labels 2026-04-05 20:33:04 +02:00

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#152