2026.3.2 Release Notes

2026.3.2 Release Notes

[Source: https://bitwarden.com/help/releasenotes/#2026-3-2]

(The listed release number is for the Bitwarden Server, other version numbers released in this cycle also include Web 2026.3.1, Browser Extension 2026.3.0, Mobile 2026.3.1, Desktop 2026.3.1, and CLI 2026.3.0.)

Password Manager

  • :star: Autofill button on View Login: Autofill credentials directly from the View Login page in the browser extension.

  • Generator options for password protected Sends: All password generator features are now available when creating password protected Sends.

  • Arm64 builds available for Linux: Arm64 desktop builds are now available for Linux users on Snapcraft and Flathub. See downloads for additional information.

 

Admin Console

 


Additions from the GitHub releases:

 

Server 2026.3.2

  • Removed feature flag for biometrics refactor on Windows
  • Removed feature flag for updated organization invitation email
  • Removed feature flag for updated organization confirmation email
  • Removed feature flag for data recovery tool
  • Removed feature flag for push notifications infrastructure updates
  • Updated tax logic for Switzerland
  • Various under-the-hood improvements and minor bug fixes

Thank you! :blue_heart: A big shout-out to the following community members for their contributions!

mdusher - Add globalSettings.knownNetworks so that entire IP ranges can be used for trusting X-Forwarded-* headers

Warfields - Add PQC TLS Support

 

Web Vault 2026.3.1

  • Admins can now enable automatic confirmation of new members
  • Updated welcome experience for new users
  • Users subject to the organization data ownership policy will now be prompted to transfer their My Vault items to My Items
  • Sends can now use generated passwords
  • Various under-the-hood improvements and minor bug fixes

 

Browser extension 2026.3.0

  • Popout windows will now respect vault timeout settings
  • Users subject to the organization data ownership policy will now be prompted to transfer their My Vault items to My Items
  • Sends can now use generated passwords
  • Various under-the-hood improvements and minor bug fixes

 

Desktop app 2026.3.1

  • Users subject to the organization data ownership policy will now be prompted to transfer their My Vault items to My Items
  • Sends can now use generated passwords
  • Various under-the-hood improvements and minor bug fixes

 

CLI 2026.3.0

  • Removed password reset flows from CLI. Accounts required to set or reset a password will now see an error message when logging in
  • Various under-the-hood improvements and minor bug fixes

 

Android Password Manager 2026.3.1 (21415) – Overview

What’s New

  • Policy changes apply instantly, no manual sync needed
  • Clear archived items directly from your vault

Improvements

  • Clearer menu labels and in-app prompts
  • Better screen reader labels and icon contrast
  • Passphrase generator and password history fixes

Bug Fixes

  • Fixed crashes related to autofill, navigation, and screen loading
  • Fixed duplicate items after TOTP QR code scans
  • Fixed passkey creation failing for certain apps
  • Fixed verification codes not syncing
  • Org transfer decline no longer creates a blank log entry

 

Android Authenticator 2026.3.1 (1478) – Overview

  • Fixed an issue where scanning QR codes could create duplicate items.
  • Various under-the-hood bug fixes and improvements

 

iOS Password Manager 2026.3.1 (3062) – Overview

What’s New

  • iOS now prompts you to enable Bitwarden as a credential provider directly from the app
  • Organization policy changes take effect immediately

Improvements

  • Clearer labels for Send and vault buttons
  • Browser extension imports handle profile switching and search without closing the screen
  • More graceful TOTP edge case handling
  • Better stability for login-with-device notifications

Bug Fixes

  • Archiving a vault item as org owner no longer shows a false error
  • Declining an org transfer no longer creates a blank audit log entry
  • Fixed a loop prompting repeated encryption setting updates
  • Biometric unlock works correctly for keychain users with session timeout policies
  • Fixed a crash when transferring items from the browser extension

 

iOS Authenticator 2026.3.1 (545) – Overview

  • Various under-the-hood bug fixes and improvements

 


To keep everything in one place, new versions within this Release cycle will be added to this first post. (and I only report the Release Notes here as they can be found in the official Bitwarden Release Notes and in the released versions in the Bitwarden GitHub repositories – I’m not a Bitwarden employee)

:warning: Some new features may be behind a feature flag, so it can take a few days for those features to get “activated” by Bitwarden. (in rare cases, new features can also temporarily be disabled again via those feature flags when there are unforeseen issues)

Features marked with a :star: Star icon are part of a progressive rollout.

:warning: Some Bitwarden apps/clients are distributed by “stores” (like Apple’s App Store, Microsoft Store, Google Play Store, Mozilla’s Extension store…) so the availability of new versions via those channels also depends on the approval processes of these “stores” and thereof the respective roll-out can take some time.

For those who self-host their Bitwarden server: some new features of a given release cycle might only arrive / get activated in one of the next release cycles on self-hosting environments.

2 Likes

Appreciate the new functionality, but hate the UI design. The Autofill function in the view page is really a secondary option to the main autofill feature that is available in the Vault view, so it makes no sense for it to be so prominent in the View Login view. And placing it below the organization/collection/folder tags pushes essential information out of view — when implementing UI changes, it is important to remember that the primary function of the View Login view is to view the data stored in the vault item (e.g., password, websites, notes, etc.), which is now more difficult.

Any of the following designs would have been better:

 

I would love to hear from anybody on the design team whether they would (or did?) consider above alternatives.

1 Like

Hm, following your mock-ups, I guess you should add, that it wouldn’t be better – in your view – if the new autofill button would be above the organization/collection/folder tags. :wink:

Overall, I think I could also have lived with your design suggestions – but one thing I do like about the new button (besides it’s sheer existence): the target is now larger again, which makes it more easy clickable than a small “Fill button”. (it was criticized back then – as we got the new browser extension UI – by many, that the Fill button would be too small of a target)

Assuming that this bug is fixed or that this FR is implemented, how often do you really think that you will be using the new Autofill button, as compared to autofilling from the Vault view?

Users who want a large click target are already accommodated by the option “Click items in autofill suggestion to fill”. If necessary, a similar option could also work on the View Login screen (“Click item name to fill”).

Alternatively, in my first mockup, the “Autofill” button is already much larger than the standard Fill button, and could be even further expanded in size without reducing the information content of the View Login screen.

Now that my extension has upgraded to 2026.3.0, I really dislike the UI design. The new Autofill button is by far the most visually prominent item in the View Login view (and is more prominent even than the item name). I would even call the new button “jarring” in appearance.

I hope that @Mary_Blabaum has seen my redesign proposals above

1 Like

If it were held to a vote, mine would go for the one with “autofill” adjacent to and similar in appearance to “edit”.

Also, there is now an “archive” link next to the trash can.

I agree that the Autofill button should be in the bottom toolbar, so that it remains accessible with one click, even if scrolling down (since one use-case of autofill from the View Login view is wanting to review account details to confirm that one is autofilling the correct account).

However, I would be OK with either version of the button, and placements either in a button group on the left, or in an icon group on the right (which may or may not include the archive icon. depending on subscription plan), or even by itself in the center…