# Vaultwarden vulnerabilities in Docker

**URL:** <https://vaultwarden.discourse.group/t/vaultwarden-vulnerabilities-in-docker/5047>\
**Category:** Uncategorized\
**Created:** [June 15, 2026, 5:49am UTC](https://vaultwarden.discourse.group/t/vaultwarden-vulnerabilities-in-docker/5047 "2026-06-15T05:49:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jolinar](https://avatars.discourse-cdn.com/v4/letter/j/67e7ee/32.png) [@jolinar](https://vaultwarden.discourse.group/u/jolinar)\
**Post date:** [June 15, 2026, 5:49am UTC](https://vaultwarden.discourse.group/t/vaultwarden-vulnerabilities-in-docker/5047/1 "2026-06-15T05:49:53Z")

</div>

Recently I’ve been using DockerHand to analyse my containers, specifically the vulnerability section, and it returned this result for Vaultwarden. The file also shows that there is an option to address the issues by updating several external dependencies.

[https://gofile.me/7PjyL/bkj8Vyeec](https://gofile.me/7PjyL/bkj8Vyeec)

Sorry for my English.

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [June 17, 2026, 8:29pm UTC](https://vaultwarden.discourse.group/t/vaultwarden-vulnerabilities-in-docker/5047/2 "2026-06-17T20:29:49Z")

</div>

Updating dependencies from the package manager of a container is normally not best practice. Also, most of those files are not used.

If you want less dependencies which are outdated or vulnerable i would suggest to use the Alpine based containers.