Repository navigation
Update vaultwarden/server Docker tag to v1.37.4 - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.37.3-alpine→1.37.4-alpineRelease Notes
dani-garcia/vaultwarden (vaultwarden/server)
v1.37.4Compare Source
Security Fixes
This release contains security fixes for the following advisories. We strongly advise updating as soon as possible.
These are private for now, pending CVE assignment and publishing at a later date.
Upgrade notes
IP_HEADER=X-Forwarded-For, the client IP is now the rightmost address that isn't inIP_HEADER_TRUSTED_PROXIES(it used to be the leftmost). If you have several proxies in a row, for example a CDN in front of nginx, add all of them toIP_HEADER_TRUSTED_PROXIES. Otherwise the address of the proxy in front is used for rate limiting and logs.bw send receiveon CLI 2026.4.2 and older no longer works, the same as against Bitwarden's own servers since v2026.8.0. Creating and managing Sends works on all clients.ssh-agent,ssh-key-vault-item,mutual-tls,anon-addy-self-host-alias,simple-login-self-host-alias,pm-25373-windows-biometrics-v2,pm-26340-linux-biometrics-v2,desktop-ui-migration-milestone-1to-4,cxp-import-mobileandcxp-export-mobile. IfEXPERIMENTAL_CLIENT_FEATURE_FLAGSstill lists one of them, startup logs a warning and saving settings in the admin panel fails until it's removed.DUO_USE_IFRAME(the deprecated Traditional Prompt) is removed and ignored if set.email/recover_twofactor, sent after a login with a two-step recovery code.POST /identity/accounts/registerandPOST /api/accounts/preloginendpoints are removed. No current client uses them.What's Changed
pm-32009-new-item-typesfeature flag by @bdd in #7478pm-34171-card-scannerfeature flag by @bdd in #7477undetermined-cipher-scenario-logicfeature flag (closes #7801) by @cad0p in #7802New Contributors
Full Changelog: dani-garcia/vaultwarden@1.37.3...1.37.4
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.