[PM-33979] Not possible to add a "Login with passkeys"-passkey using Firefox

[pamperer562580892423]

Steps To Reproduce

1. Important: Open the Web Vault in Firefox (my current version: 148.0.2) - and on Windows 11, in case it's OS-dependant!
2. Log in and go to Settings --> Security --> Master Password --> Log in with passkey
3. Click on 'New passkey' and try to add a BW-login-passkey

Expected Result

Windows Hello comes up and I can add a passkey wherever I want. (e.g. on my hardware security key)

Actual Result

The Windows Hello pop-up doesn't come up at all, but instead the web vault directly shows an error message (see below) - so, in the end, I can't create a BW-login-passkey for my BW account/vault.

Screenshots or Videos

The error message that I get instead of Windows Hello popping up:

Additional Context

• Only happens on Firefox 148.0.2 for me. [EDIT May 25, 2026: That was the Firefox version at the time I wrote this issue report. I have no idea when that bug "started" - and with which Firefox version. Or if it is connected to a specific change in Firefox at all, but rather with a change in the web vault, making it "incompatible" with Firefox here. ?!]
• I didn't test other Firefox forks though.
• E.g. Vivaldi works as it should.
• so I would guess it at least doesn't affect Chromium-based browsers (?!)
• interestingly, the creation of a 2FA-passkey for the Bitwarden account/vault is not affected, but this still works as expected on Firefox (and this probably shows also, that it's not a general bug on e.g. Firefox's side, as via Firefox the Windows Hello passkey prompt still evidently can be triggered - but just not via the "New (login) passkey" route in the web vault)
• this other issue showed a similar thing with Firefox not showing a passkey prompt - maybe there is a connection?!
• and there are other reports about passkey prompts not coming up on Firefox mobile in connection with the BW Android app - though I don't have this issue myself on my Android 15 device, there still might be a connection
• all in all, I would suspect there was a change on Firefox regarding passkeys - and either it's a bug that Firefox has to resolve, or it's some changes that the BW clients/apps have to adapt to (just speculation - please investigate this properly 😉)

PS: This issue was mentioned here on the Community Forum as well - and there is another thread about this issue directly: https://community.bitwarden.com/t/passkey-creation-in-firefox-fails/95162

Operating System

Windows

Operating System Version

11 Home 25H2 (Build 26200.8039)

Web Browser

Firefox

Browser Version

148.0.2

Build Version

Web vault 2026.3.0 (EU server region account)

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-33979
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-33979

[SergeantConfused]

Hi @pamperer562580892423,

Thank you for your report. This is already being tracked and investigated internally (I also encountered this myself), and I'll keep this GitHub report open for now for external visibility; please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

By the way, the two GitHub reports you linked are related to storing passkeys within Bitwarden, which is different from enrolling a Login Passkey.

Thank you again,

[pamperer562580892423]

@SergeantConfused Thanks!

By the way, the two GitHub reports you linked are related to storing passkeys within Bitwarden, which is different from enrolling a Login Passkey.

Yeah, I know. I just listed all those issues as it looks a bit like Firefox changed something with passkey prompt handling and that might have ramifications in different places...

But of course, those could also be completely separate issues. 🤷

[pamperer562580892423]

Short update: no change with the new Firefox 149.0.

[Miguel-Bento-Github]

Changing my Firefox privacy settings from strict to standard made it work again.

[pamperer562580892423]

@Miguel-Bento-Github Thanks for your post! - And interesting! I had that on "Custom" and played a bit around with it now... but even when I set it to "Standard", the web vault still doesn't allow any login-passkey to be created (same error message as before).

So, that may play a role - but it can't be all. 🤔

[prym0rdial]

Changing my Firefox privacy settings from strict to standard made it work again.

I just tried this solution on Firefox 152.0.2 and it did not generate the Hello prompt.

[pamperer562580892423]

I just tried this solution on Firefox 152.0.2 and it did not generate the Hello prompt.

@prym0rdial Thanks for adding that. Could you clarify if you're using Firefox Nightly or something? (the current stable is FF 150 and not FF 152...)

I also just tested it on Firefox 150.0.2 again and it still doesn't work for me.

[prym0rdial]

I just tried this solution on Firefox 152.0.2 and it did not generate the Hello prompt.

@prym0rdial Thanks for adding that. Could you clarify if you're using Firefox Nightly or something? (the current stable is FF 150 and not FF 152...)

I also just tested it on Firefox 150.0.2 again and it still doesn't work for me.

My apologies - I just looked and I mistyped the version. I am on 150.0.2 (64-bit).

[beedell-roke]

@pamperer562580892423, does issues/11218#issuecomment-2718417776 relate to this? ¹

Footnotes

1. community.bitwarden.com/t/97003/3 ↩

[pamperer562580892423]

@pamperer562580892423, does issues/11218#issuecomment-2718417776 relate to this? 1

Footnotes

1. community.bitwarden.com/t/97003/3 ↩

@RokeJulianLockhart Honestly, I'm not sure. - Since you used Firefox, it could be. But you reported it in Sept 2024 - and I have no idea when this issue here (that it's impossible to create a BW login-passkey on Firefox at all) started.

I think you could test your issue with a Chromium-based browser now. If you get the same result as before, it maybe (probably) is not related to this issue here. ?!