mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-24 17:12:43 -05:00
[GH-ISSUE #6729] Compatibility Issue: Bitwarden CLI 2025.12.0 fails with "User Decryption Options are required" on older Vaultwarden versions #11334
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vaultwarden#11334
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SionS4R on GitHub (Jan 17, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6729
Prerequisites
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
Client Environment
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 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
@BlackDex commented on GitHub (Jan 17, 2026):
Closing as a duplicate and already fixed.