mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-07-18 01:49:32 -05:00
[GH-ISSUE #7366] Bitwarden Firefox autofill prefers custom field named Username over login username #39935
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jay-tau on GitHub (Jun 23, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/7366
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.36.0
Deployment method
Other method
Custom deployment method
Hosted on PikaPods.
Reverse Proxy
PikaPods-managed reverse proxy (
X-Forwarded-Foraccording to diagnostics).Host/Server Operating System
Linux
Operating System Version
PikaPods-managed Linux container host; diagnostics reports linux/x86_64, container base Debian.
Clients
Browser Extension
Client Version
Bitwarden Firefox extension v2026.5.1; Firefox 151.0.4; client OS Linux / CachyOS.
Steps To Reproduce
real-user@example.com.Usernamewith valuecustom-field-user.Expected Result
The website username field is filled with the login item's username value:
real-user@example.com.Actual Result
The website username field is filled with the custom field value:
custom-field-user.Logs
Screenshots or Videos
No response
Additional Context
This was first reported to Bitwarden clients as https://github.com/bitwarden/clients/issues/21312. Bitwarden closed that issue because the reproduction was against Vaultwarden and asked for issues to be reported only when reproduced against an official Bitwarden server.
I searched existing open and closed Vaultwarden issues for this specific
Usernamecustom-field/autofill behavior and did not find a duplicate. The nearest generic autofill reports I found were unrelated, such as #6978 (iOS click-to-fill behavior).I am filing this here because the confirmed repro is currently against Vaultwarden. It may still ultimately be client-side autofill precedence, but it would be useful to know whether Vaultwarden stores/returns the login username and custom field named
Usernamedifferently from official Bitwarden in a way that triggers this behavior.@stefan0xC commented on GitHub (Jun 23, 2026):
I don't think this is Vaultwarden specific. Can't you reproduce that using the Bitwarden Cloud as backend? See https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting for how to go about issues with a Bitwarden client.