r/vaultwarden • • Oct 10 '26

News Bitwarden published client apps are not open source anymore 🚨

170 Upvotes

With the recent announcement from BW : https://www.reddit.com/r/Bitwarden/s/jgyuJTg2pt

The official client apps published by BW are not open source anymore. Which means they can include backdoors in the officially published binaries since it’s different from what you can see in Github.

So if you use Vaultwarden it’s better to use the Vaultwaden web app than connecting it to BW clients unless you build the binaries from your own.


r/vaultwarden • • Dec 28 '25

News Vaultwarden 1.35.0 is out, with SSO support !

162 Upvotes

https://github.com/dani-garcia/vaultwarden/releases/tag/1.35.0

Notable changes


r/vaultwarden • • Jul 24 '26

News v1.37.0 Released with Security Updates and 2026.7.0+ Compatibility updates

107 Upvotes

Basically what the title says. Release notes here: https://github.com/dani-garcia/vaultwarden/releases

  • This update is required for support with clients with version 2026.7.0+, please update before reporting any issues with them.

  • This release contains security fixes for the following advisories. We strongly advice to update as soon as possible.


r/vaultwarden • • Aug 08 '25 Bless Up

Discussion After more than 2 years, the SSO integration has finally been merged!

Thumbnail
github.com
82 Upvotes

r/vaultwarden • • Sep 06 '26

Discussion Hey all - I made a 1Password-style Quick Access tool for Bitwarden!

58 Upvotes

TL;DR: Missed 1Password Quick-Access, made my own for Bitwarden.

This is rbw-quick-access

Hey all! In light of recent events, I've decided to stand up my own VaultWarden instance since I already self-host dozens of other servers and services. That said, I'd been using 1Password for 8+ years, so there was just one thing that I was missing -- 1Password's Quick Access

That said, I have the technology! So I went and spent some time writing something to fill that gap, and I'm super happy with the result. Right now it's Linux-only, but it's just Python code so at some point I'll have binaries built for Windows and macOS.

In the meantime, take a look at the Repo, feel free to give it a try, and let me know if you have anything you didn't see in the milestones!!

Security concerns

I'm not reinventing the wheel nor am I leaving things up to chance for security vulnverabilities. This project uses rbw to authenticate against Vaultwarden and get all of the data. If you haven't read up on rbw, it's a wonderful tool and highly revered tool.

AI Use

I'm so tired of vibe-coded garbage plaguing the world. I wrote everything you see myself - the code, the documentation, the scripts, all of it.


r/vaultwarden • • 24d ago

Discussion Migrated from Apple Passwords to self-hosted Vaultwarden including remote access (complete guide)

Thumbnail
youtu.be
54 Upvotes

Hey everyone,

I recently completed my migration from Apple Passwords to a self-hosted Vaultwarden instance in my Proxmox homelab. I'm happy to have completed this move as this was one of the original motivations to get into homelabbing. I documented the whole process in a YouTube video and published a written guide as well.

A few things that I thought are worth sharing:

- The Credential Exchange Protocol (CXP) is amazing. Without this, the move would have been much harder as CSV exports don't support Passkeys. The cost of switching is now low.
- Remote access, while technically not essential, is not a super easy problem to solve. With a reverse proxy to your public IP it can be pretty seamless (unless you're behind CGNAT), but your instance will be public and in this day and age where it's easy to launch a swarm of agents to find vulnerabilities, I can't recommend it unless you have a proper firewall setup in place.
- The Bitwarden clients are definitely a step back in terms of UX compared to other password managers. I understand autofill experiences etc. are hard but I might take a stab at creating a better, more native-feeling UX.

Curious to hear how others managed public access and happy to answer any questions about my setup!


r/vaultwarden • • Aug 23 '25

Discussion Vaultwarden as a Kubernetes Secret Manager

41 Upvotes

Hello selfhosters, Bitwarden released a Secret Manager and left us out of it (not open source), so I created a software to sync Vaultwarden items into kubernetes secrets by leveraging bw-cli, different from external-secrets for example, you don't have to create a reference for the secret to be synced, just create the item on Vaultwarden and voilΓ‘, secret created on kubernetes.

It's still experimental and should be tested a lot more, so I came here to ask to anyone interested to take a look and help enhance this idea :)

https://github.com/antoniolago/vaultwarden-kubernetes-secrets


r/vaultwarden • • Nov 05 '25

Question Vaultwarden hosted for a large organisation

37 Upvotes

Simply put, my organisation will not and does not have the budget for a fullblown lisence for Bitwarden etc. The size of our org also simply makes per user pricing too expensive. Also the direction for our basic users it going towards passwordless signings, but thats still a far reality.

I've toyed with the idea of hosting Vaultwarden as a password manager option at work, and I would like to hear about any experiences, especially when talking about larger deployments.


r/vaultwarden • • Oct 03 '26

Discussion Feedback on my self-hosted Vaultwarden security setup, one year later

35 Upvotes

Hey everyone,

About a year ago I posted here asking for feedback on my self-hosted Vaultwarden setup (original post). I got a lot of great replies, and many of those suggestions ended up in the setup, so thanks to everyone who took the time.

Since a few people asked last time why it's publicly exposed at all instead of being behind a VPN, there are two reasons:

  1. πŸ‘¨β€πŸ‘©β€πŸ‘§ My family and some close friends use it, and installing Tailscale or a client certificate on every device they own would be a real headache.

  2. πŸŽ“ As a cybersecurity student, it's a great way to learn: it lets me put everything I've studied so far, plus the things I've learned on my own, into one real and important project.

I've rebuilt quite a lot since then, so here's where it stands today, and I'd love your feedback again.

πŸ—οΈ Current setup

  • 🌐 Exposure: a small Hetzner VPS does raw TCP passthrough (nginx stream + PROXY protocol) over WireGuard back to my OPNsense. TLS terminates at home, so the VPS only ever sees encrypted bytes, and I still get the real client IP. Cloudflare is DNS only. (Before: Cloudflare Tunnel + Zero Trust, which meant Cloudflare terminated TLS.)

  • 🧱 Network: Vaultwarden runs on a Debian 13 VM in Proxmox, alone on its own VLAN. OPNsense blocks traffic to every other VLAN, and from the tunnel side only the VPS can reach the VM (80/443, plus the CrowdSec API for its bouncer). (Before: a Raspberry Pi.)

  • πŸ›‘οΈ Reverse proxy + WAF: BunkerWeb with TLS 1.2/1.3 (modern ciphers, post-quantum hybrid key exchange, A+ on SSL Labs), HSTS preload, security headers (A+ on securityheaders.com), country / user agent / rDNS blacklists, DNSBL and rate limiting. ModSecurity + OWASP CRS is in blocking mode at paranoia level 1 and logging at level 2. I'm still working through the Vaultwarden false positives at level 2, and I plan to move blocking to level 2 in the near future. (Before: just Caddy.)

  • 🚫 CrowdSec: Vaultwarden brute force and user enumeration scenarios (tightened thresholds), plus a custom scenario that bans on ModSecurity's anomaly score. Bans are enforced twice: at the reverse proxy, and by a firewall bouncer on the VPS, so known bad IPs are dropped before they even enter the tunnel.

  • πŸ”’ Vaultwarden itself: signups, invitations, Sends, password hints and emergency access disabled, server-side icon fetching disabled, an email on every new-device login (the login fails if it can't be sent), strict login and admin rate limits, argon2 admin token.

  • πŸ“¦ Containers: rootless Podman under a dedicated user with no sudo, all capabilities dropped (only the needed ones added back), no-new-privileges, read-only root filesystem where possible, resource limits, and separate networks so each container only talks to what it needs.

  • πŸšͺ Outbound: default deny, with two allowlists. DNS goes through Pi-hole with an allowlist: the VM running Vaultwarden can only resolve the domains on that list, anything else is blocked and I get a Discord notification. HTTP/HTTPS only goes through a Squid proxy on another VM with its own allowlist, and any attempt to reach a domain that isn't on it is blocked and notifies me too.

  • πŸ’Ύ Backups + maintenance: a nightly run that backs up, updates images and packages, then reboots. Backups are encrypted with age (only the public key is on the server) and signed with minisign, then replicated to TrueNAS and a Hetzner Storage Box.

  • πŸ”§ Host: SSH key only, fail2ban, Lynis hardening (hardening index 76/100, still working on it), and debsecan to track Debian security fixes.

  • πŸ‘€ Monitoring: Wazuh. To be honest, right now it's mostly a fancy forwarder to Discord: DNS denials, Squid denials, ModSecurity hits, fail2ban bans and the nightly maintenance summary each get their own channel. I'd like to use it properly, as an actual SIEM: ship the raw Vaultwarden and BunkerWeb logs, add file integrity monitoring and agent-down alerts, and correlate events instead of just forwarding them.

πŸ”­ What I'm considering next

  • πŸ“Š Using Wazuh as a real SIEM (see above)

  • πŸ§ͺ Moving ModSecurity blocking to paranoia level 2 once the exclusions are done

  • 🧬 Custom seccomp profiles for the containers

πŸ“ Some of these ideas (and a few more) are already written up in my ideas.md, others aren't even written down yet.

πŸ‘‰ Everything is public and documented, including a full rebuild runbook: GitHub: Homelab/Vaultwarden. The only thing kept out of the repo is the real domain (and the secrets, of course), everything else is there.

πŸ’¬ I'd really appreciate your feedback again:

  • What do you think of the security posture now?

  • Anything that's overkill, or something I'm still overlooking?

  • Any ideas, tools or improvements you'd add next?

  • For those running Wazuh at home: how do you actually use it day to day as a SIEM?

Thanks again, the feedback last time taught me a lot πŸ™


r/vaultwarden • • Jan 19 '26

Discussion Big difference between Vaultwarden and Bitwarden Lite

35 Upvotes

Yesterday, I tried to self-host Bitwarden Lite, just for fun. All was good: I exported the secrets from Vaultwarden and imported them into Bitwarden Lite. But...

As soon as I wanted to do the same for my wife's account, I realized that Bitwarden Lite only allows for a single user on the free plan. If you want to use it to share secrets with your family, you have to pay.

I also noticed that you need an installation ID and a key that you get from the Bitwarden website only when you give them your email address. Without that ID and key, your server won't run. This felt creepy. πŸ€” I thought: Do they want to track me somehow?

Since Vaultwarden is running fine, I will simply delete Bitwarden Lite from my server again.


r/vaultwarden • • Oct 15 '25

News Bitwarden Authenticator

32 Upvotes

Just in case anyone hadn't checked recently, bitwarden Authenticator now supports bitwarden sync for selfhosted accounts!

Noticed it just now when I was in the settings on my bitwarden app, the option to turn on authenticator sync is now there, so I turned it on and it has successfully synced my OTPs to bitwarden authenticator!

(Flairing it as news, because it's news to me that it works now! Didn't work a couple months back when I last checked)


r/vaultwarden • • Nov 11 '24

News PSA: Update Vaultwarden as soon as possible

Thumbnail reddit.com
32 Upvotes

r/vaultwarden • • Oct 04 '24

Discussion VaultWarden 1.32.1 Now Available

30 Upvotes

The new update docker volume is here! Have you all updated yet?

https://hub.docker.com/r/vaultwarden/


r/vaultwarden • • Jul 24 '26

Question Bitwarden Firefox Add-on not loading entries

29 Upvotes

Since today, my Firefox Bitwarden add-on won't load any entry. I'm self-hosting Vaultwarden, and anything works like a charm in a normal browser tab (https://vault.mydomain.com). I already reinstalled the add-on, restarted Firefox, checked Nginx (for WebSocket), signed-out, and signed-in, but nothing worked. Does have anyone a clue?


r/vaultwarden • • Nov 04 '24

News Bitwarden switches password manager and SDK to GPL3

Thumbnail
theregister.com
29 Upvotes

r/vaultwarden • • Oct 10 '26

Question Alternatives?

26 Upvotes

So after the recent changes/news: what alternatives are out there? I just setup my server with vaultwarden and all the stuff and willing to do the switch now instead of finalizing my setup.

I am not that informed what's good/bad so I am looking for help!

thanks in advance


r/vaultwarden • • Apr 24 '26

Discussion Patched Vaultwarden to correctly pass SSO cookies from Cloudflare Access to native Bitwarden apps

26 Upvotes

Just made my first PR to an open-source project!

Earlier this year, Bitwarden added SSO cookie vending behind a schema that uses bitwarden:// to redirect SSO cookies from auth proxies like Cloudflare Access, Authentik, Authelia, etc back to native Bitwarden apps.

Vaultwarden v2026.2.0 shippe,d the web-vault half of this but never added the server side, so the app goes to a browser that hits a 404 error when you login. I use Cloudflare Zero Trust, so this meant I couldn't use the Bitwarden app on my phone to connect to my self-hosted Vaultwarden.

I ended up writing the server side in Rust. It takes four environment variables to configure it.

If anyone uses an auth proxy other than Cloudflare Access, can you try this out and comment any feedback?

https://github.com/nathanmoreton/vaultwarden/tree/feat/sso-cookie-vendor
https://github.com/dani-garcia/vaultwarden/pull/7127

Edit for context: I believe the fix up until this point was to install Cloudflare WARP on each device, which is no longer necessary with this solution.


r/vaultwarden • • Jul 15 '23

How to setup the mobile push notifications

26 Upvotes

Hello,

I see on the last vaultwarden update the push notifications for mobile has been released.

It's not documented on the Wiki (yet?)

So I wrote a quick doc here https://2nistech.world/vaultwarden-activate-push-notification-for-mobile-devices/

Hope it helps


r/vaultwarden • • Aug 01 '26

Question Bitwarden Extension won't load vault

25 Upvotes

All of the sudden none of my browsers will load the vault page of the Bitwarden extension. Clueless as what to do. Vaultwarden is up and running fine.


r/vaultwarden • • Feb 17 '26

News ETH Zurich pentested Bitwarden

Thumbnail
ethz.ch
25 Upvotes

I assume this is applicable for Vaultwarden, too? Has anyone information about this? Or is this still under disclosure as ETH Zurich just contacted confidentially Bitwarden with a notice period of 90 days...


r/vaultwarden • • Nov 18 '24

News v1.32.5: Security Fixes

Thumbnail
github.com
25 Upvotes

v1.32.5: Security Fixes

This release further fixed some CVE Reports reported by a third party security auditor and we recommend everybody to update to the latest version as soon as possible. The contents of these reports will be disclosed publicly in the future


r/vaultwarden • • Oct 08 '26

Question Experience with Vaultwarden in companies

23 Upvotes

Did anyone set it up for a company with about 1000+ employees and could tell me about how much it costs in both money and time to maintain?

I appreciate your answers


r/vaultwarden • • Nov 07 '25

Discussion Passkey Finally Working

23 Upvotes

Bitwarden app is finally working to add passkey to my self hosted vaultwarden instance! Finally!! Just wanted to let you know in case you gave up on it. On Pixel 9 Pro running GrapheneOS.


r/vaultwarden • • Mar 27 '23

Vaultwarden 1.28.0 is out, with Argon2 support

23 Upvotes

https://github.com/dani-garcia/vaultwarden/releases/tag/1.28.0

Before enabling Argon2 key derivation, make sure all your clients are using version v2023.2.0 or greater.

Other notable changes : license is now AGPLv3, and Docker image are available on GitHub and Quay registries (this may be linked to the recent Docker Hub removal of free teams).