v1.37.2 (Upgrade to this version when using clients v2026.8.0+)

[BlackDex]

Note

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

What's Changed

• Fix Debian cross-linking with xx-cargo by @alexliluz in Fix Debian cross-linking with xx-cargo #7524
• Fix playwright test by @Timshel in Fix playwright test #7548
• Misc fixes and updates by @BlackDex in Misc fixes and updates #7558
• Include user email in successful login logs by @lmogthb in Include user email in successful login logs #7496
• Fix sendmail executable permission check by @p-boenisch in Fix sendmail executable permission check #7483
• add dummy revisionDate by @stefan0xC in add dummy revisionDate #7608

New Contributors

• @alexliluz made their first contribution in Fix Debian cross-linking with xx-cargo #7524
• @lmogthb made their first contribution in Include user email in successful login logs #7496
• @p-boenisch made their first contribution in Fix sendmail executable permission check #7483

Full Changelog: 1.37.1...1.37.2

---

This discussion was created from the release 1.37.2.

[BlackDex]

There is a chance you need to clear the cache or try a force sync with your client.
If clearing the cache is difficult, most of the time you can try these steps and see if that works.

First, be 100% sure you have updated to the latest version of Vaultwarden!
Check your /admin/diagnostics page, check the start logs or validate via the version command.

Do one of the following to be sure.

• Go to https://my.domain.tld/admin/diagnostics check for issues and the version is up-to-date.
• Check the logs during the startup of Vaultwarden, it should state something like this:
  • Running current testing: Version 1.37.1-46d71107
  • Running current latest: Version 1.37.2
• Check via docker exec:

  docker exec vaultwarden /vaultwarden --version

  It should return something like this:
  • Running current testing:

    Vaultwarden 1.37.1-46d71107
    Web-Vault 2026.7.0

  • Running current latest:

    Vaultwarden 1.37.2
    Web-Vault 2026.7.0

After that, try these steps in the following order until you can login.

• Fully logout, and log in again
• Clear the cache of the App, Desktop App, Extension etc... (Sometimes after clearing a restart of the Browser/Device might help too)
• Uninstall and then Reinstall the App, Extension (And restart the Browser/Device). This will probably not work for the Desktop/CLI clients.

Follow these steps first before posting anything that you can still not login, it will only clutter the discussion and issues and will not help.

[Creepios]

We have rolled out the extension to many users and ms edge is (unfortunately) auto updating the extensions. So is there any chance to clear the cache of this extension on mass rollout scale?

[jpagh]

For what it's worth, my Edge extension just worked, as well as the desktop app, after updating Vaultwarden.

Edit: I ended up reinstalling the Edge extension. I was having an issue syncing and that fixed it.

[kent-unwin]

Confirming login works successfully after removing the installed version of client from Edge and then reinstalling.

Vaultwarden 1.37.2
Web-Vault 2026.7.0

Edge Client version: 2026.8.0

[porjo]

Confirming issue: solved for me with Firefox on Linux: simply reinstalling was not sufficient, I had to remove the extension's storage (about:debugging -> inspect -> clear 'Extension Storage'), then reinstall extension.

[hosaka]

@porjo did the same but instead of reinstalling the extension simply restarting the browser was enough (after logging in again of course)

[timkgh]

When is Fill Assist coming, please?

[Handrail9]

Hi, I am confused about something. I have updated my docker container, and docker exec vaultwarden /vaultwarden --version shows me being on v1.37.2, while admin/diagnostics says I'm on v1.37.1. I tried stopping vaultwarden, doing a docker prune, and manually adding the 1.37.2 tag, but the WebUI still reports v1.37.1 after bringing it back up.

I can't figure out why this is happening. I can't log into the extension anymore even after a full uninstall/reinstall of the extension. Did I do something wrong?

[BlackDex]

Maybe you are running two vaultwarden's?

[Handrail9]

Maybe you are running two vaultwarden's?

Somehow, yes this was the problem. It looks like I managed to have a duplicate compose file that I must've forgotten about. Sorry for asking about something so silly.

Thank you!

[bfren]

Note for those in multi-user setups on macOS - I used AppCleaner to completely remove the Bitwarden Desktop app and browser extension from one user account, and got it working - but it was still broken in my other user (work) account. I had to close the Desktop App, manually delete ~/Application Support/Containers/Bitwarden, then reopen it to login successfully.

[IAMJDA]

Deinstallation and reinstallation of the browser plugins is a PITA. We have BitLocker Extension as forced extension rolled out to all clients. Now, that we removed the Intune policy, the plugin gets uninstalled automatically everywhere and users need to manually reinstall it, set up the manual login again etc.

[stratacast]

I wound up rolling back to an older version of the extension and disabled auto updates on the Bitwarden extension. It has not been the fault of Vaultwarden that Bitwarden has been breaking compatibility so much this year, but the dance is getting tiring. Thank you for the great work in getting timely updates out!

[oSumAtrIX]

The proxy-cookie-redirect-connector.html fails behind Cloudflare Zero Trust

[BlackDex]

That is probably a Cloudflare setting which needs to be re-configured i guess.
Not something which can be resolved on the server side.

[hbel]

With the current version, I am experiencing problems when Users log out completely from the WebUI. Currently, even users deactivated 2FA are not able to log in again (seems to me like the WASM interface is broken "again" because BW changed it "again"). Browser Extension and App are working like a charm though.

[BlackDex]

Please check /admin/diagnostics if there are possible issues with the headers.
Also, sometimes some security/ad-block extensions also cause weird issues like this, check the networking tab of the browsers Developer console to see if there are errors reported regarding this.

[hbel]

Great, there seemed to be a problem with the content-security headers we could actually fix. 😊