Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / Vaultwarden / 1.37.1

Vaultwarden 1.37.1

WAIT

Release notes signal caution: If you have applied any workaround to fix this locally, please revert those fixes to prevent possible other issues.

Published: 2026-07-29T13:40:10Z · GitHub release

Summary of changes

## Note This patch release resolves the issues with invites. If you have applied any workaround to fix this locally, please revert those fixes to prevent possible other issues. I'm sorry that it took some time to check and validate this fix. Also, this release fixes an issue (#7475) with all the Alpine based images which are build using https://github.com/BlackDex/rust-musl/. An issue with the build image OpenSSL compilation is resolved and those are used to build the new alpine tagged containers. ## What's Changed - Always send initOrganization and orgUserHasExistingUser in invite URL by @vikfox in #7482 - Indirectly resolved #7475 by using newer rust-musl build images which had a compilation issue with OpenSSL. ## New Contributors - @vikfox made their first contribution in #7482 Full Changelog: 1.37.0...1.37.1

Breaking changes

None detected by heuristics.

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

2

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.