mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-06 09:13:03 +03:00
Trashbin shows entries from other orgs #124
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 @senpro-ingwersenk on GitHub.
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, HIBP_API_KEY, SIGNUPS_ALLOWED, ADMIN_TOKEN, IP_HEADER, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD, SMTP_ACCEPT_INVALID_CERTS, SMTP_ACCEPT_INVALID_HOSTNAMES
Config:
Vaultwarden Build Version
1.33.2
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Traefik via k3s 1.32.1
Host/Server Operating System
Linux
Operating System Version
NixOS 24.11
Clients
Web Vault
Client Version
Diverse
Steps To Reproduce
Expected Result
Only entries belonging to this organization should be visible.
Actual Result
An absolute lot of entries from many, many other organizations are visible. The org itself only has ~27 entries - the bin has...a whole lot more (I didn't dare counting, and couldn't figure out how to do so using the database)
Logs
Screenshots or Videos
This screenshot was taken in an org with only the mentioned 20ish records:

And this one was taken in one that had many, many more:

Since those include the names of our customers in full, I blacked them in Paint. However, neither of them should see any of those entries whatsoever, at all, ever.
Additional Context
We were trying to find a way to improve the performance of our clients (Extension, Desktop) by clearing out the bins and were under the belief that each org had it's own bin. But whilst my collegue was cleaning, he noticed that some orgs showed more or less entries, and eventually he saw that many of those entries were in fact shared, where they shouldn't be.
Further, we were just considering to let our customers access their own credentials in the org associated to them - and now we are worried that they would've seen others' deleted entries.
To gather further information, I went into
psqland\d'd my way around the scheme to figure out where the flag was for deleted records to see how exactly they were handled - but, I didn't find it, possibly and most likely overlooked it no less.Since I am not entirely sure if this is a bug or not, I decided to post it as a ticket. Because if it is, it's perhaps a problem.
Thank you and kind regards!