When a security-stamp gets reset/rotated we should also rotate all device refresh-tokens to invalidate them. Else clients are still able to use old refresh tokens.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dani-garcia/vaultwarden/pull/7031
**Author:** [@BlackDex](https://github.com/BlackDex)
**Created:** 3/29/2026
**Status:** ✅ Merged
**Merged:** 3/29/2026
**Merged by:** [@dani-garcia](https://github.com/dani-garcia)
**Base:** `main` ← **Head:** `login-fixes`
---
### 📝 Commits (1)
- [`9caedb8`](https://github.com/dani-garcia/vaultwarden/commit/9caedb8c8a42782b47730a58266ff8d1ff125e8a) Rotate refresh-tokens on sstamp reset
### 📊 Changes
**6 files changed** (+46 additions, -17 deletions)
<details>
<summary>View changed files</summary>
📝 `src/api/admin.rs` (+2 -2)
📝 `src/api/core/accounts.rs` (+16 -8)
📝 `src/api/core/emergency_access.rs` (+1 -1)
📝 `src/api/core/organizations.rs` (+2 -1)
📝 `src/db/models/device.rs` (+17 -1)
📝 `src/db/models/user.rs` (+8 -4)
</details>
### 📄 Description
When a security-stamp gets reset/rotated we should also rotate all device refresh-tokens to invalidate them. Else clients are still able to use old refresh tokens.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/7031
Author: @BlackDex
Created: 3/29/2026
Status: ✅ Merged
Merged: 3/29/2026
Merged by: @dani-garcia
Base:
main← Head:login-fixes📝 Commits (1)
9caedb8Rotate refresh-tokens on sstamp reset📊 Changes
6 files changed (+46 additions, -17 deletions)
View changed files
📝
src/api/admin.rs(+2 -2)📝
src/api/core/accounts.rs(+16 -8)📝
src/api/core/emergency_access.rs(+1 -1)📝
src/api/core/organizations.rs(+2 -1)📝
src/db/models/device.rs(+17 -1)📝
src/db/models/user.rs(+8 -4)📄 Description
When a security-stamp gets reset/rotated we should also rotate all device refresh-tokens to invalidate them. Else clients are still able to use old refresh tokens.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.