2026.4.1 Release Notes

[Nail1684]

2026.4.1 Release Notes

[Source: https://bitwarden.com/help/releasenotes/#2026-4-1]

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

Password Manager

• Change master password on extensions and desktop: You can now change your master password on browser extensions and desktop apps. To support future improvements, workflows that allowed a master password change via the CLI were removed.

• Desktop UI updates: The desktop app UI has been updated with visual improvements.

• Click to autofill by default: Within the browser extension, you can now click anywhere on an item within Autofill suggestions to insert your credentials. This update removes the Fill button and Click items in autofill suggestions to fill setting for a more streamlined appearance.

• Updated Clear Clipboard default: The browser extension’s Clear Clipboard setting now defaults to five minutes, an extra precaution to help keep your credentials secure.

• mTLS support now on iOS: Both the iOS and Android mobile apps now support uploading mTLS certificates for self-hosted servers that require client authentication. Upload your certificate when you set your server URL.

• Attachment status loading bar: Uploading an attachment on the desktop app and browser extension will display an upload status bar.

• Keeper JSON importer: You can now import data from Keeper with a JSON file.

 

---

Additions from the GitHub releases:

 

Server 2026.4.1 – Overview:

• Removed feature flag for automatic member confirmation settings
• Removed feature flag for unlock with passkey
• Removed feature flag for SCIM refactor
• Various under-the-hood improvements and minor bug fixes

 

Server 2026.4.2 – Overview:

• Bug fix for subscription handling

 

Web Vault 2026.4.2 – Overview:

• Added event logs for phishing blocker
• Refactor unlock service to use Bitwarden SDK
• Updated account recovery to include managing member two-step login methods
• Updates to prevent losing unsaved changes when creating a Send
• Updated default clipboard clearing time to 5 minutes
• Various under-the-hood improvements and minor bug fixes

 

Browser extension 2026.4.0 – Overview:

• Refactor unlock service to use Bitwarden SDK
• Compact mode no longer in beta
• Updated default clipboard clearing time to 5 minutes
• Various under-the-hood improvements and minor bug fixes

 

Browser extension 2026.4.1 – Overview:

• Performance improvements to reduce the extension’s impact on web page loading and responsiveness

 

Desktop app 2026.4.0

• Targeted performance improvements on read/write
• Refactor unlock service to use Bitwarden SDK
• Updates to prevent losing unsaved changes when creating a Send
• Updated default clipboard clearing time to 5 minutes
• Various under-the-hood improvements and minor bug fixes

 

CLI 2026.4.2

• Security fix for local storage of API keys
• Various under-the-hood improvements and minor bug fixes

 

Android Password Manager 2026.4.1 (21464) – Overview:

Bug Fixes

• Fixed looping alert in encryption settings
• Fixed passkey creation for related-origin sites
• Archived items no longer appear in Verification Codes
• Fixed TOTP countdown freezing when returning to the app in some occasions

 

Android Password Manager 2026.4.2 (21562) – Overview:

• Fix crash on startup for F-Droid build
• Fix for missing search option during autofill
• Fix for login issues on devices running 32bit Android

 

Android Authenticator 2026.4.1 (1526) – Overview:

• General under-the-hood improvements and bug fixes.

 

iOS Password Manager 2026.4.1 (3112) – Overview:

What’s New

• Support for client certificate authentication (mTLS) for self-hosted environments
• Your User ID is now visible in the Debug view with a one-tap copy button

Improvements

• Authenticator menu bar now displays correctly on iOS 26 when biometric unlock is enabled

Bug Fixes

• Fixed autofill occasionally closing when using long press

 

iOS Authenticator 2026.4.1 (593) – Overview:

• General under-the-hood improvements and bug fixes.

 

---

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)

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 icon are part of a progressive rollout.

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.

[grb]

@Nail1684

Click to autofill by default: Within the browser extension, you can now click anywhere on an item within Autofill suggestions to insert your credentials. This update removes the Fill button and Click items in autofill suggestions to fill setting for a more streamlined appearance.

This is bad news for UX. We’re evidently going to be back to having different behavior (autofill or view) when performing the same action (clicking an item), depending on context.

Is there going to be a “View” quick-action button again, or are we now going to have to use the “More Options” menu to open an item?

I predict that this change is going to be very unpopular for users who have a large number of autofill suggestions (and for users who prefer UX consistency).

And what was so bad about giving users the option to disable “Click items to fill”? I don’t see any real benefit of this change.

[DenBesten]

@Nail1684

Click to autofill by default:

JFYI, this bullet point has resulted in this FR being closed as implemented:
   ✅ Make "Click items to autofill on Vault view" the default

And this FR being reopened as it no longer is implemented:
   Consistent behaviour on clicking a listed item in vault

[Neuron5569]

@djsmith85 ,

The browser 4.1 release note has “regressed” to an uncategorized list.

The unreadable list is still better than the previous no-detail release notes, since I can at least use an LLM to search (hopefully somewhat accurately) for categories of interest.

[djsmith85 (Daniel James Smith)]

Releases notes have been updated.

Still working through some issues to get this fully automated.

[Lethargy7029]

The Click to autofill by default change is what brought me to the forums. I hate it. I view logins all the time for a variety of reasons. This is a serious regression.

[Nail1684]

@Lethargy7029 You probably want to join this feature request that @DenBesten posted here before: Consistent behaviour on clicking a listed item in vault

[kjlgfojoijoigjior342]

typical bitwarden engineering culture, break something that works fine for years because engineers got nothing better to do, then ask users to file a feature request to revert your effort to degrade the product. Good job as usual

click to fill by default is a significant security issue that it enters password in places user did not explicitly permit, like on the wrong subdoman with default base domain matching

[ellipsis (Adi Iepure)]

Desktop UI updates: The desktop app UI has been updated with visual improvements.

I think “visual changes” is the better term here, because these do not feel like improvements at all. To me, these are downgrades.
We now see half as many items in the list and, as far as usability goes, I now have to perform two clicks instead of one to copy the password.

I understand that you might be trying to cater to touch users, but at least add a setting to revert to the compact view and a default copy (user or password) when clicking the copy button.

You fixed something that wasn’t broken.

[Heath]

I can understand changing the default behavior “Click to autofill by default”, but removing the option to turn it off is so infuriating! I frequently need to access custom fields and notes on items and now this requires yet another click. There is no good reason to remove the ability to customize this behavior.

[TheBestPessimist]

It’s not just about ‘1 more click’. You need to move the mouse quite a lot extra, and hit quite small buttons to view the entry. The drawback is much larger than ‘linear 1 extra click’. (quite a lot of so called UX designers do not understand the basic principle in ‘Fitts’ law of computer interaction and ergonomics’)

And as a laptop touch user, this is even more annoying for me.

[grb]

@TheBestPessimist

The drawback is much larger than ‘linear 1 extra click’. (quite a lot of so called UX designers do not understand the basic principle in ‘Fitts’ law of computer interaction and ergonomics’)

And the opposite problem occurs for users who do want one-click autofill, if they need to find the relevant account by searching among the autofill suggestions — they now need to use unnecessary additional mouse movements and clicks to autofill (compared to the one-click autofill that works only in the “Autofill Suggestions” area).

Thus, beyond Fitt’s Law, the new UX also violates the UX design principle of Functional Consistency — the same action (clicking an item) produces different results depending on context, and a desired result (viewing vs. autofilling) requires different actions depending on context. Such issues are the topics of two open feature requests:

• Consistent behaviour on clicking a listed item in vault
• Restore one-click autofill for search results that match active web page

[yncx]

Adding my voice in support of the new “autofill” behaviour in browser extension UI being a bad UX. My two main issues are:

• No 1-click Edit/View action: you now have to click the context menu to access this. This is a complete dealbreaker for any item with custom fields (mainly Identities and Cards, but also many Login items). I don’t necessarily mind whether clicking the item auto-fills and a button views/edits or vice versa (Ideally, there would be a setting to choose like there was before), but there NEEDS to be a one-click action.
• Inconsistent “Autofill” vs “All Items” behaviour: it seems you can no longer auto-fill items from the “All Items” list, so any Logins without a matching URL require manually copy/pasting username and password. This seems like a regression. The behaviour should be consistent throughout the vault.

[DenBesten]

@yncx

No 1-click Edit/View action

Clicking on an item in the “search results” or the “all items” sections does view the item for me. It is just the “autofill” section that requires one to select from the ⋮ menu.

@yncx

…it seems you can no longer auto-fill items from the “All Items” list, so any Logins without a matching URL…

This exists for me in the ⋮ menu.

I am running Browser extension 2026.4.1, Chrome 148, Win 11. If you are experiencing different behavior, the difference between browsers ought to be reported as a bug.

[yncx]

@DenBesten You are indeed correct regarding the “search” & “all items” functionality, my apologies. However, I still think the behaviour should be consistent with the “auto-fill” section and there should be one-click view/edit or fill button.