c/selfhosted · by megaman@discuss.tchncs.de · 206d

Vaultwarden security update Feb 10 2026

https://github.com/dani-garcia/vaultwarden/releases/tag/1.35.3

GHSA-h265-g7rm-h337 (Publication in process, waiting for CVE assignment) This vulnerability would allow an authenticated attacker that is part of an organization to access items from collections to which the attacker does not belong

109 points · 14 comments · view on lemmy.world

14 Comments

tofu@lemmy.nocturnal.garden · 22 pts · 206d (7 replies)

Already updated yesterday 🤓 All hail the mighty renovate

Natanox@discuss.tchncs.de · 2 pts · 206d (4 replies)

Renovate?

tofu@lemmy.nocturnal.garden · 7 pts · 206d

I have all my compose stacks in git. They're deployed from their git repos with Komodo.

Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there's a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It's a great semi automatic way to handle updates without giving up control.

There's a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

qaz@lemmy.world · 1 pts · 206d (2 replies)

It's a bot to create PR's with dependency updates

Natanox@discuss.tchncs.de · 2 pts · 206d (1 reply)

Might be a stupid question, but how are PR's connected to your server deployment?

tofu@lemmy.nocturnal.garden · 2 pts · 205d

Copying my other comment. It opens PRs to change the tag from the docker image.

I have all my compose stacks in git. They’re deployed from their git repos with Komodo.

Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.

There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

motruck@lemmy.zip · 1 pts · 206d (1 reply)

Renovate? Hrmmmm

tofu@lemmy.nocturnal.garden · 4 pts · 206d

Hrmmm?

osanna@thebrainbin.org · 7 pts · 205d (4 replies)

one thing I'm not willing to self host is vault/bitwarden. My whole life is based in my password manager. I imagine Bitwarden inc has a lot better security than me, and if I lose access to it I'm stuffed.

Auli@lemmy.ca · 4 pts · 204d

What are they going to get an encrypted blob.

keyez@lemmy.world · 3 pts · 204d

Bitwarden was the second thing I ever self hosted. On a local server on a UPS and hasn't really been an issue across 7 years. Every so often I save an encrypted JSON on my main laptop to use with keepass if there's ever an issue where the server is down for a while.

nopermissions@lemmy.ml · 3 pts · 205d (1 reply)

Had this exact thing happen to me. I was hosting vaultwarden on a raspberry pi and then it fell over. My client devices had caged versions of my vault, but I couldn’t make changes to it. I quickly moved over to Bitwarden and it’s been fantastic.

osanna@thebrainbin.org · 1 pts · 204d

yup, BW is awesome. and mostly free. I use BW too, but not self hosted.

oyzmo@piefed.social · 2 pts · 204d

Vaulwarden is the best 😁 selfhosted for 3 years, no problems. Got all my devices on my tail/headscale network, and only addresses allowed to my server are lan and tailscale 🤓