I’ve had an issue with the Chrome extension (11.0) where I’m frequently being prompted for updating login credentials for Bank of America, Fidelity, and a few others even though there is nothing to update. The username/password is the same, but Bitwarden is treating it like I’ve updated the username or password and wants me to update Bitwarden with new information.
I still get the prompts even with the domains excluded in Settings > Notifications > Excluded Domains.
Is this a known bug? AFAIK, nothing has changed with my setup unless I did so unintentionally or a recent Chrome update did it. I’m using Chrome 142.0.7444.162 on macOS 26.2 beta 2.
No one complaining about this issue (either here or on Github) has provided any example URLs for testing, so until an affected user comes forward with the requested information, it is not possible to reproduce or troubleshoot the issue (much less to fix it!).
Clearly I have no access to your internal services, so I will not be able to do any troubleshooting using the information you have provided. A “pattern” is not required, I just need one or more specific examples of publicly available online login forms where this issue allegedly occurs.
@grb I think we have a testing site – someone from the corresponding GitHub issue stated it would happen on any two step auth site… so I just tested it on the forum. And this (using the inline autofill menu with unchanged login data) triggered it for me indeed. (seems I didn’t experience it before, because I usually use passkey login for the forum)
Though I’m not a 100% sure about this, as I have too many (invalid) test login data items for the forum in my vault also, which may interfere in my case…
PS: Okay, I deleted some invalid test items… and what I reported here in this post is still reproducible for me.
I’m running extension version 2025.11.0 on Edge version 142.0.3595.80 and it’s prompting to update my login credentials on all websites that I log in to, including community.bitwarden.com. I’ve also tested on:
online dot adp dot com
amazon dot com
adminconsole dot adobe dot com
Sorry for the weird formatting, I was only allowed to post one link.
(it was closed recently, but if there are more reports and if Bitwarden can reproduce it they probably will reopen it… I can reproduce the issue at the moment → UPDATE: that issue was re-opened)
Yeah I may have to do that until Bitwarden fixes it. Thanks for the suggestion. Even with the annoying update popups, I still will never go back to LastPass. LOL
UPDATE: There was an option for ask to update login. I unchecked it. Hopefully that stops it.
Open a browser profile, login to Microsoft Admin centre which brings up the above link for authentication
Extension through previous history suggests the login to autofill
Login with autofill or copy and paste
Now:
Same as above, but after submitting the username and password, Bitwarden extension offers to “Update” every login with the URL above configured for it (I’m an MSP, many Microsoft logins)
Experienced the same with another web portal to which there are multiple different accounts in Bitwarden for. The logins offered to be updated seem to match the auto-fill URI, not random logins.
This is a concern for myself and my team, as someone could easily click update on a different login, and invalidate the password for that account.
When I login to certain sites, a small window opens and asks whether I want to update my login. Even I click Update, the message repeats every time I open the site and try to login. If it matters, cookies associated with these sites are persistent and don’t get deleted. Is thee a fix for this? Thanks.
Short notice: I updated the title of this thread fromFrequent notices to update login with latest Bitwarden Chrome extensiontoFrequent notices to ‘Update existing login’ / ‘Save (new) login’ with latest browser extensions.
I though I’d try the option to disable the notifications for a known problem domain before I disabled the notifications globally by unchecking the two respective options, add/update login. I refreshed the page as instructed, but the issue persisted on that domain. Perhaps I did something wrong, but it seems that only the global settings may work for this issue, and maybe that’s why adding domains was not suggested.
Though I’m not a 100% sure about this, as I have too many (invalid) test login data items 
for the forum in my vault also, which may interfere in my case…
