2026.5.0 Release Notes

Announcements Release Notes
1

2026.5.0 Release Notes

[Source: https://bitwarden.com/help/releasenotes/#2026-5-0]

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

Password Manager

  • :star: Devices list now available on desktop: The Devices list is now available on the desktop app, alongside the web app and browser extension, to surface devices that your account has been used on.

  • Biometrics integration now available on Flatpak and Snap: Biometric unlock of browser extensions, usable through an integration with the Bitwarden desktop app, is now available on Flatpak and Snap distributions.

  • :star: Web app quick actions: Launch a website and copy vault data from new quick actions buttons, available by hovering over an item in the web app.

  • Send UI update: Selecting a Send item in the browser extension and web app will now display a View screen instead of routing directly to the Edit screen.

 

Admin Console

  • :star: Blumira SIEM integration: Teams and Enterprise organizations can now integrate with Blumira for security and event management (SIEM).

  • Expanded account recovery options: Account recovery now supports revoked members and can reset two-step login methods.

  • Revoked member reason: There’s a new tooltip next to each member on the Members → Revoked page that explains why members were revoked from your organization.

  • Updated event logs: Password Manager now saves when an attachment is added to an organization-owned item, using the existing Created attachment for item event.

 

Self-host

Helm Chart v2.0: Version 2.0 of the self-host Helm chart will includes two breaking changes:

  • NGINX ingress is now disabled by default in this version of the chart. The chart includes support for Gateway API as an alternative.

  • The image.name field has been removed from values.yaml. Any configurations using image.name must be updated to use image.repository instead.

  • :warning: Note

    Before upgrading to this version of the chart, review these changes and update your values file accordingly. For additional information on setting up or migrating to Gateway API, refer to Helm Traffic Routing.

 

Additions from the GitHub releases:

 

Server 2026.5.0

 

Web Vault 2026.5.0

 

Browser extension 2026.5.0

What’s Changed

  • Updated warning when autofilling on non-matching URIs
  • Various under-the-hood improvements and minor bug fixes

 

Desktop app 2026.5.0

  • Updated UI for Archive to more clearly communicate it is a Premium feature
  • Various under-the-hood improvements and minor bug fixes

 

CLI 2026.5.0

What’s Changed

  • Various under-the-hood improvements and minor bug fixes

 

Android Password Manager 2026.5.0 (??) – Overview:

(will be added when released)

 

Android Authenticator 2026.5.0 (1624) – Overview:

  • Various under-the-hood bug fixes and improvements

 

iOS Password Manager 2026.5.0 (??) – Overview:

(will be added when released)

 

iOS Authenticator 2026.5.0 (??) – Overview:

(will be added when released)

 

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 with one of the next release cycles on self-hosting environments.

3 Likes