I would guess neither nor.
Extension 2026.6.0 indeed already is available via the Chrome Store, so I just triggered the update manually, also on Vivaldi.
It seems to me that the extension has a new permission that has to be accepted for re-enabling (and why it was automatically disabled, I think):
(that popup was shown when I clicked “check” / Überprüfung)
Hm. I think the change might be that it was an optional permission before – only triggered when one tried to activate biometric unlock in the extension – and now it seems to be a “default” permission.
I would guess this has something to do with the development of Shared Unlock. Maybe @Quexten could enlighten us – if he stopped by… 
PS: @mutilator I now updated the extension on other browsers and it seems only Vivaldi throws that “dramatic” message… 
Vivaldi, the drama queen 
Hi! This is expected. We default enabled the permission instead of asking for it on-demand when you enable biometric unlock. This allows the extension to communicate with the desktop app, if you have it installed. While this introduces a on-time prompt for existing installations, for new installations there no longer is any permissions prompt needed. This is in preparation for shared unlock as @Nail1684 mentions but also affects biometric unlock in the extension.
The desire here is for things to “just work”, since the current biometric setup is quite complex and a frequent point of frustration for customers.
EDIT: I’m not sure what setting I changed, but I restarted my browser entirely again, and the issue has gone away. Leaving this post here in case others have the same issue.
Even after accepting the new permission, I still get the same error when opening any new browser window in my profile:
I have another profile with 2026.5.1 of the extension installed, and that’s behaving normally.
What’s the fix for this with Vivaldi? Having to close a spurious dialog every time I open a new window is getting a little annoying.
My limited Portuguese suggests this is the same as the error I had. My troubleshooting involved:
It would be useful to see if any of these fix the issue for you
That Edge wording is the generic Chromium warning for the native messaging permission. In this case it is expected for Bitwarden 2026.6.0: the extension needs that channel for desktop-app integration / biometric unlock. I would still check the boring basics: extension installed from the official store, version matches the published Bitwarden release, and the desktop app is current. If you do not use desktop unlock/integration, leaving the permission accepted is not the same as giving random sites access to your vault; it just lets the extension talk to its native host.
I’m seeing this behavior in Vivaldi but a separate issue that may or may not be related. When I open a new Vivaldi window, whether from a desktop shortcut, from the V/File menu, or by splitting my current window with another extension (Tab Resize), I’m getting a popup saying the Bitwarden extension was automatically disabled even though it is still present and functioning. Is this part of the side panel issue or should I post this as a separate bug?
@requa, I have moved your post to a topic that discusses the error you are getting.
