That seems to be the same behavior as the web-vault version that's used in the Bitwarden Cloud. So if you have an account you might want to replicate it with upstream and (if there are no similar existing issues) report that upstream.
Cf. https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting for more information.
@stefan0xC commented on GitHub (Jan 9, 2026):
That seems to be the same behavior as the web-vault version that's used in the Bitwarden Cloud. So if you have an account you might want to replicate it with upstream and (if there are no similar existing issues) report that upstream.
Cf. https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting for more information.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ludopaquet on GitHub (Jan 9, 2026).
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.35.1
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
traefik
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Web Vault
Client Version
v2025.12.1
Steps To Reproduce
Expected Result
Attachment should be displayed after the action
Actual Result
The Attachment is not listed
Logs
Screenshots or Videos
Additional Context
No response
@stefan0xC commented on GitHub (Jan 9, 2026):
That seems to be the same behavior as the web-vault version that's used in the Bitwarden Cloud. So if you have an account you might want to replicate it with upstream and (if there are no similar existing issues) report that upstream.
Cf. https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting for more information.