Search of URI fields yields unexpected results for regular expressions and URIs containing exclamation mark (!)

[bwbug]

Steps To Reproduce

1. Create a login item named Example1_Regex, containing the URI string xxxxxTESTSTRINGyyyy, with the URI match detection method set to "Regular Expression".
2. Create a login item named Example2_Exclamation, containing the URI string https://www.example.com/login!, with the URI match detection method set to "Base domain".
3. Search for TESTSTRING.
4. Search for >login.uris:*TESTSTRING*.
5. Search for https.
6. Search for >login.uris:https*.

Expected Result

• In Step 3, expect the search results to include the item Example1_Regex.
• In Step 4, expect the search results to include the item Example1_Regex.
• In Step 5, expect the search results to not include the item Example2_Exclamation.
• In Step 6, expect the search results to not include the item Example2_Exclamation.

Actual Result

In Version 2025.8.0 and earlier:

• In Step 3, search results include the item Example1_Regex (as expected).
• In Step 4, search results include the item Example1_Regex (as expected).
• In Step 5, search results do not include the item Example2_Exclamation (as expected).
• In Step 6, search results do not include the item Example2_Exclamation (as expected).

 

In Versions 2025.9.0–2025.10.0:

• In Step 3, search results include the item Example1_Regex (as expected).
• In Step 4, search results include the item Example1_Regex (as expected).
• In Step 5, search results include the item Example2_Exclamation (contrary to expectations).
• In Step 6, search results include the item Example2_Exclamation (contrary to expectations).

 

In Versions 2025.11.0 and later:

• In Step 3, search results do not include the item Example1_Regex (contrary to expectations).
• In Step 4, search results do not include the item Example1_Regex (contrary to expectations).
• In Step 5, search results include the item Example2_Exclamation (contrary to expectations).
• In Step 6, search results include the item Example2_Exclamation (contrary to expectations).

Screenshots or Videos

No response

Additional Context

Exclamation marks are not reserved characters, and can be found in the wild — e.g., "hashbangs" such as https://www2.personas.santander.com.ar/obp-webapp/angular/#!/login.

Search behavior should be stable, and not change from version to version. Thus, there have been at least two regressions since version 2025.8.0.

The faulty search behavior is also present in the Desktop app and in the Web Vault.

Operating System

Windows

Operating System Version

Windows 11 (23H2)

Web Browser

Chrome

Browser Version

No response

Environment Versions

Version: 2025.12.0; SDK: 'main (0107af7)'; Server version: 2025.12.0.

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

[daniellbw]

Hi there,

This issue has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!