Servers and applications
GHSA-rxhg-2pw9-vf25
Send max_access_count can be exceeded by concurrent access requests
- Severity
- Medium 5.3
- Published
- 3 Oct 2026
- Last changed
- 3 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 1.37.0
- Weakness
- Race condition (CWE-362)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Sources
- Project advisories (GitHub)
Description
Vaultwarden does not enforce a Send's max_access_count atomically. The access-count check and the increment are separate operations, so concurrent requests can all pass the check before any of them writes, allowing more accesses than the sender configured.
File: src/api/core/sends.rs
Both Send access endpoints read access_count, compare it against max_access_count, then write access_count + 1 as a separate operation, with no database-level locking:
Two concurrent requests against a Send at access_count = 0, max_access_count = 1: both read 0, both pass the check, and both write access_count = 1. Both return the secret — the text content for a text Send, or a signed download token for a file Send.
The write compounds the problem. save() persists the whole row from memory, so one request's stale in-memory value overwrites another's increment rather than adding to it. The stored counter can therefore under-report the number of accesses that actually succeeded.
Affected software
| Software | Affected versions |
|---|---|
VaultwardenServers and applications · github:dani-garcia/vaultwarden |
|
About Vaultwarden
Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
- Docker Hub pulls
- 361,463,423Docker Hub, 15 Nov 2026
- GitHub stars
- 70,745GitHub, 15 Nov 2026
- Forks
- 3,457GitHub, 15 Nov 2026
- Latest release
- 1.37.5GitHub, 15 Nov 2026
- Released
- 1 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 17 Feb 2018GitHub
Vulnerabilities in Vaultwarden
- In our list
- 41
- Published in the last 12 months
- 31
- Critical, last 12 months
- 1
- High, last 12 months
- 8
- Known exploited
- 0
- GHSA-7ccc-c43j-4p36Organization member can move personal items into an organization without collection accessMedium 4.3 28 Oct 2026
- GHSA-69q9-v8p6-xvx3Revoked or unconfirmed organization member retains read and delete access to organization ciphersHigh 8.1 28 Oct 2026
- GHSA-q5x6-grh5-fqgcUnbounded client-declared attachment fileSize causes an out-of-bounds panic that permanently breaks vault sync for every user who can see the cipherMedium 6.5 28 Oct 2026
- GHSA-v576-3wvq-xh3cLoop-carried user_created flag in send_invite deletes a pre-existing user's account and entire vault when an invite e-mail failsMedium 6.8 28 Oct 2026
- GHSA-64mc-4p6f-r7x9Revoked or unconfirmed organization Admin can read cipher audit logsMedium 4.3 28 Oct 2026
- GHSA-qwx4-wcv4-mpcvOrganization Admin can revoke and delete Owners through an Admin-mintable organization API keyLow 3.8 28 Oct 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-rxhg-2pw9-vf25
- github.com https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-rxhg-2pw9-vf25