2025.12.0 Release Notes

[Nail1684]

2025.12.0

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

Password Manager

• Vault health alerts and password coaching: As a new feature for Premium plans, browser extensions will now alert users that they should update a password when it’s detected that the password is weak, re-used, or exposed and recommend that they be updated.

• Direct import for Chrome and Brave: Transfer your data from Chrome and Brave browsers into Bitwarden quicker than ever with direct import.

• Autofill and save URI: In the browser extension, the option to Fill & save has been rolled into the normal Autofill option. Now, when selecting Autofill for an item without a matching URI, an option to save the current website URI to the login item will appear.

Admin Console

• Prevent SSO login for revoked users: Users that have been revoked from an organization will no longer be able to use SSO to log in to their SSO-linked account.

 

---

Additions from the GitHub releases:

 

Server 2025.12.0

• Block SSO login for SSO-linked users not in a confirmed or accepted status
• Removed feature flags
• Various under-the-hood improvements and minor bug fixes

 

Web Vault 2025.12.0

• Updated Premium callouts and signup experience
• Small performance improvement when logging in
• Various under-the-hood improvements and minor bug fixes.

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

calvinballing - Spellcheck bugs

 

Browser extension 2025.12.0

• Improved warning interface when auto-filling on a non-matching website
• Added direct import option from Chrome
• Updated Premium callouts and signup experience
• Small performance improvement when logging in
• Various under-the-hood improvements and minor bug fixes.

Thank you! A big shout-out to the following community members for their contributions!
calvinballing - Spellcheck bugs

 

Desktop app 2025.12.0

• Update for self-hosted to re-add the ability to unlock with Windows Hello following app restart.
• Added direct import option from Chrome
• Updated Premium callouts and signup experience
• Small performance improvement when logging in
• Various under-the-hood improvements and minor bug fixes.

Thank you! A big shout-out to the following community members for their contributions!
calvinballing - Spellcheck bugs

 

CLI 2025.12.0

• Multiple improvements to policy enforcement and synchronization
• Enhanced security with automatic KDF upgrades and updated dependencies
• Various under-the-hood performance and stability improvements

 

Android Password Manager 2025.12.0 (21003) – Overview

• Improved autofill compatibility with Samsung Internet, Opera, and Edge browsers
• Fixed app crashes when unlocking during sync errors
• Fixed passkey creation for AliExpress
• General under-the-hood improvements for usability and performance

 

Android Authenticator 2025.12.0 (1114) – Overview

• General under-the-hood improvements for usability and performance (–> source)

 

iOS Password Manager 2025.12.0 (2787) – Overview

• Fixed master password strength indicator to only appear after entering 12 or more characters
• Improved performance when searching for passwords and logins
• Improved Autofill performance when browsing passwords and passkeys
• Updated supported languages

 

iOS Authenticator 2025.12.0 (375) – Overview

• General under-the-hood improvements for usability and performance

 

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 – I’m not a Bitwarden employee)

[grb]

@Nail1684

Vault health alerts and password coaching: As a new feature for Premium plans,

I have significant trepidations/concerns about this, since I see no mention in the documentation that this feature will be optional, or that it will be possible for a user to dismiss the warning banner. Many users store passwords that are weak but cannot be made stronger (e.g., voicemail PINs, padlock combination codes, passwords for services with overly restrictive password length rules). Having a non-dismissible perma-nag banner displayed in the apps and extensions will not only be an annoyance and waste of screen real estate, but also make it likely that users do not notice or act on real alerts (e.g., in case of a future password breach).

 

@Nail1684

Autofill and save URI: In the browser extension, the option to Fill & save has been rolled into the normal Autofill option.

Not a fan of this either, since it makes the workflow more complex and cumbersome.

[Nail1684]

@grb

@Nail1684

Vault health alerts and password coaching: As a new feature for Premium plans,

I have significant trepidations/concerns about this, since I see no mention in the documentation that this feature will be optional, or that it will be possible for a user to dismiss the warning banner.

That was also one of my first thoughts… I also have some 4-digit-PINs in my vault and it would be very annoying if that would be a permanent notification.

In general, the feature itself sounds great to be honest – as “automatic vault health reports” (and in other apps than only the web vault) is a long-standing feature request.

@grb

@Nail1684

Autofill and save URI: In the browser extension, the option to Fill & save has been rolled into the normal Autofill option.

Not a fan of this either, since it makes the workflow more complex and cumbersome.

I can understand that. – Though, I always had the impression, that the distinction between those two options Autofill and Fill and save was not very obvious (and certainly not self-explanatory) either.

[grb]

@Nail1684

Though, I always had the impression, that the distinction between those two options Autofill and Fill and save was not very obvious

My thoughts on this are:

• I don’t understand the use-case for “Autofill” (without saving) — is this variant really necessary?
• I wish Bitwarden would implement a “pro”/“poweruser” mode, in which we could trigger different functions with click, shift-click, etc. In that case, there could be a single “Autofill” option/button/menu item, and using modifiers (Shift or Ctrl, etc.) could determine whether the URL is also saved.

[John1307 (John)]

Hi, may I ask when this Version will be released for Firefox?

[Nail1684]

@John1307 Well, the browser extension was (as always) released for all supported browsers on GitHub. From what I understand, it also is/was sent to the different “browser stores” – and it varys how long they take until they approve it and release it on their stores.

Firefox/Mozilla store usually takes the longest. Anything is possible now – from a few days to a few weeks.

[grb]

@grb

I have significant trepidations/concerns about this, since I see no mention in the documentation that this feature will be optional, or that it will be possible for a user to dismiss the warning banner.

My fears have now been substantiated, so I have created a feature request:

Options to disable or dismiss permanent "Change at-risk password" warnings

As of version 2025.12.0, Premium subscribers have been saddled with a new feature that displays a permanent (non-dismissible) warning banner stating "  Change at-risk password, when viewing items for which Bitwarden has determined that the password is “at-risk”. Bitwarden needs to provide the users the option to dismiss these warnings on a per-item basis (so that the warning banner is never displayed again). I personally would also like an option to disable this new feature altogether…

[metaphase]

My Microsoft Edge browser has just updated to this and I now cant access my vault - I enter my password and get a constant spinner…

Chrome is still on 2025.11.1 and working OK. Is anyone else experiencing the same?

[grb]

@metaphase

Is anyone else experiencing the same?

No, I do not see such an issue when I unlock the Bitwarden browser extension version 2025.12.0 on Edge (or Chrome). Maybe try uninstalling and reinstalling?

[metaphase]

Yep that’s what I had to do - it’s fixed it but of course due to lack of settings sync I had to go through and set everything up again. Here’s hoping it’s not the same for every machine & browser!