Bug bounty program · HackerOne
Most upvoted reports11
- #1929915ValidBypass for forced re-authentication upon biometrics changeBitwarden · Authentication · 2023–37votes
- #272570ValidOrganization Admin Privilege Escalation To OwnerBitwarden · Input Validation and Logic · 2017–28votes
- #289000ValidVulnerable exported broadcast receiverBitwarden · Misconfiguration and Insecure Design · 2017–24votes
- #925527ValidBlind HTTP GET SSRF via website icon fetch (bypass of pull#812)Bitwarden · Server-Side Request Forgery · 2020–21votes
- #1874155ValidBiometric key is stored in Windows Credential Manager, accessible to other local unprivileged processesBitwarden · Cryptography · 2023–19votes
- #272357ValidMailgun misconfiguration on email.bitwarden.comBitwarden · Input Validation and Logic · 2017–17votes
- #913276ValidServer-Side Request Forgery in "icons.bitwarden.net"Bitwarden · Server-Side Request Forgery · 2020–13votes
- #979820ValidRate limits too low for email 2FABitwarden · Authentication · 2020–11votes
- #1206799ValidWhen uploading attachments, unencrypted file names are made available to the serverBitwarden · Cryptography · 2021–8votes
- #337189ValidTracking Bitwarden firefox addon usersBitwarden · No weakness recorded · 2018–7votes
Subdomains77
4 covered by the program's own scope · 0 first seen this week
77 names
| Name | Scope | First seen |
|---|---|---|
| bid47bv.22371289m.bitwarden.com | Not in the scope | 2026-11-14 |
| admin.bitwarden.comadmin | Not in the scope | 2026-11-14 |
| adr.bitwarden.com | Not in the scope | 2026-11-14 |
| api.bitwarden.comapi | In scope | 2026-11-14 |
| artifacts.bitwarden.com | Not in the scope | 2026-11-14 |
| assets.bitwarden.com | Not in the scope | 2026-11-14 |
| bassets.bitwarden.com | Not in the scope | 2026-11-14 |
| billing.bitwarden.com | Not in the scope | 2026-11-14 |
| blog.bitwarden.com | Not in the scope | 2026-11-14 |
| www.blog.bitwarden.com | Not in the scope | 2026-11-14 |
| btwh.bitwarden.com | Not in the scope | 2026-11-14 |
| bws.bitwarden.com | Not in the scope | 2026-11-14 |
| cdn.bitwarden.com | Not in the scope | 2026-11-14 |
| checkout.bitwarden.com | Not in the scope | 2026-11-14 |
| community.bitwarden.com | Not in the scope | 2026-11-14 |
| company.bitwarden.com | Not in the scope | 2026-11-14 |
| components.bitwarden.com | Not in the scope | 2026-11-14 |
| contributing.bitwarden.com | Not in the scope | 2026-11-14 |
| contributing-internal.bitwarden.cominternal | Not in the scope | 2026-11-14 |
| dd.bitwarden.com | Not in the scope | 2026-11-14 |
| demo.bitwarden.comtest | Not in the scope | 2026-11-14 |
| diana.bitwarden.com | Not in the scope | 2026-11-14 |
| dl.bitwarden.com | Not in the scope | 2026-11-14 |
| docs.bitwarden.com | Not in the scope | 2026-11-14 |
| events.bitwarden.com | Not in the scope | 2026-11-14 |
| fillassist.bitwarden.com | Not in the scope | 2026-11-14 |
| fmtrack1.bitwarden.com | Not in the scope | 2026-11-14 |
| fmtracks.bitwarden.com | Not in the scope | 2026-11-14 |
| forms.bitwarden.com | Not in the scope | 2026-11-14 |
| func.bitwarden.com | Not in the scope | 2026-11-14 |
| func2.bitwarden.com | Not in the scope | 2026-11-14 |
| geeks.bitwarden.com | Not in the scope | 2026-11-14 |
| get.bitwarden.com | Not in the scope | 2026-11-14 |
| go.bitwarden.com | Not in the scope | 2026-11-14 |
| url4499.go.bitwarden.com | Not in the scope | 2026-11-14 |
| url8843.go.bitwarden.com | Not in the scope | 2026-11-14 |
| help.bitwarden.com | In scope | 2026-11-14 |
| host.bitwarden.com | Not in the scope | 2026-11-14 |
| icons.bitwarden.com | Not in the scope | 2026-11-14 |
| identity.bitwarden.comauth | In scope | 2026-11-14 |
| lewebapp.bitwarden.com | Not in the scope | 2026-11-14 |
| link.bitwarden.com | Not in the scope | 2026-11-14 |
| mail.bitwarden.commail | Not in the scope | 2026-11-14 |
| o1.mail1.bitwarden.commail | Not in the scope | 2026-11-14 |
| mobileapp.bitwarden.com | Not in the scope | 2026-11-14 |
| n8n.bitwarden.com | Not in the scope | 2026-11-14 |
| nobileapp.bitwarden.com | Not in the scope | 2026-11-14 |
| notifications.bitwarden.com | Not in the scope | 2026-11-14 |
| onyx.bitwarden.com | Not in the scope | 2026-11-14 |
| pdf-convert.bitwarden.com | Not in the scope | 2026-11-14 |
| portal.bitwarden.com | Not in the scope | 2026-11-14 |
| preview.bitwarden.comstaging | Not in the scope | 2026-11-14 |
| o2.ptr4810.bitwarden.com | Not in the scope | 2026-11-14 |
| o1.ptr996.bitwarden.com | Not in the scope | 2026-11-14 |
| push.bitwarden.com | Not in the scope | 2026-11-14 |
| qa.bitwarden.comtest | Not in the scope | 2026-11-14 |
| cdn.qa.bitwarden.comtest | Not in the scope | 2026-11-14 |
| sales.bitwarden.com | Not in the scope | 2026-11-14 |
| scim.bitwarden.com | Not in the scope | 2026-11-14 |
| sdk-api-docs.bitwarden.comapi | Not in the scope | 2026-11-14 |
| selfhost.bitwarden.com | Not in the scope | 2026-11-14 |
| send.bitwarden.com | Not in the scope | 2026-11-14 |
| shelfhost.bitwarden.com | Not in the scope | 2026-11-14 |
| shj.bitwarden.com | Not in the scope | 2026-11-14 |
| shop.bitwarden.com | Not in the scope | 2026-11-14 |
| simian.bitwarden.com | Not in the scope | 2026-11-14 |
| sso.bitwarden.comauth | Not in the scope | 2026-11-14 |
| start.bitwarden.com | Not in the scope | 2026-11-14 |
| status.bitwarden.commonitoring | Not in the scope | 2026-11-14 |
| support.bitwarden.com | Not in the scope | 2026-11-14 |
| techdiagrams.bitwarden.com | Not in the scope | 2026-11-14 |
| test.bitwarden.comtest | Not in the scope | 2026-11-14 |
| testdo.bitwarden.com | Not in the scope | 2026-11-14 |
| track.bitwarden.com | Not in the scope | 2026-11-14 |
| vault.bitwarden.comtools | In scope | 2026-11-14 |
| web-vault.bitwarden.comtools | Not in the scope | 2026-11-14 |
| www.bitwarden.com | Not in the scope | 2026-11-14 |
Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. See the subdomains on the Atlas or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-14.