Brand new Login and BW Generated PW is listed At-Risk.

[spark706]

Steps To Reproduce

This has been discussed at "https://community.bitwarden.com/t/whats-the-reason-for-the-change-at-risk-password-warning/91948/55" and repeats when I click on the Chrome extension and view the login information. I just, and I mean 30-seconds ago, made a new account with a BW generated password that is a 17 character alphanumeric - special character string which cannot be cracked in 30-seconds I am betting. I have had several of my accounts that are older show as at-risk which makes sense given they are older, but a 30-second old account, nope.

I have a premium account and appear to be using Version: 2026.1.1 SDK: 'main (8e5efd8)' Server Version: 2023.2.1

Expected Result

No at-risk notification for a 30-second old user and PW.

Actual Result

At-risk notification for a 30-second old user and PW.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Windows

Operating System Version

No response

Web Browser

Chrome

Browser Version

No response

Environment Versions

seriously, you have waht you need.

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-33286
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-33286

[pamperer562580892423]

Another user here.

I just, and I mean 30-seconds ago, made a new account with a BW generated password that is a 17 character alphanumeric - special character string which cannot be cracked in 30-seconds I am betting.

Please keep in mind, that there are three possible reasons for that "at-risk" warning:

1. "weak"
2. "reused"
3. "exposed/breached"

So, please check for those three reasons - and only when your "at-risk" item is not listed in at least one of those three corresponding Vault Health Reports, then it would be a bug.

Server Version: 2023.2.1

Either this is a typo - or you are self-hosting and using a completely outdated server version?!

[rmcdowell-bitwarden]

Hi there,

I attempted to reproduce your issue and was unable to do so. I would echo what @pamperer562580892423 mentioned in that your self-hosted server is out of date if that is accurate version number.

We use GitHub issues as a place to track bugs and other development related issues. If your issue persists, please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!