Repository navigation
Open
Labels
securityA credential, an exposure, or a control that is weaker than recordedA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)stacks/sensitive on trinity (VLAN 99)
Description
The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in vaultwarden/server. This body is rewritten by every scan, and the issue closes itself when a scan finds the pinned digest clean.
The fix is normally the Dependabot bump for this image. If upstream has not released one, the fixed versions below say what to wait for.
vaultwarden/server:1.37.5
Stacks: sensitive. Digest: sha256:4fe17f415f90087377d37c755e0ea3cf189dcc6794e49cdd2a9adbb4937d9e1f.
| Severity | ID | Package | Installed | Fixed in |
|---|---|---|---|---|
| HIGH | CVE-2026-109518 | apt | 3.0.3 | 3.0.4 |
| HIGH | CVE-2026-109518 | libapt-pkg7.0 | 3.0.3 | 3.0.4 |
| HIGH | CVE-2026-116304 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116306 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116307 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116309 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116314 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116315 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116316 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116317 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116319 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116320 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116323 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116325 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116326 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116328 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116330 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116331 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116332 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116335 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-116336 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120139 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120141 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120142 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120143 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120145 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120147 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120148 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120149 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120150 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120151 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-120153 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-14661 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-18447 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-6460 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-6467 | libpq5 | 17.11-0+deb13u1 | 17.12-0+deb13u1 |
| HIGH | CVE-2026-76844 | zlib1g | 1:1.3.dfsg+really1.3.1-1+b1 | 1:1.3.dfsg+really1.3.1-1+deb13u1 |
| HIGH | CVE-2026-85091 | zlib1g | 1:1.3.dfsg+really1.3.1-1+b1 | 1:1.3.dfsg+really1.3.1-1+deb13u1 |
Written by .github/workflows/cve-scan.yml in this run.
Metadata
Metadata
Assignees
Labels
securityA credential, an exposure, or a control that is weaker than recordedA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)stacks/sensitive on trinity (VLAN 99)
Activity
chore(deps): caddy 2.11.4 -> 2.11.7, vaultwarden 1.37.3 -> 1.37.4 (#1022
[-]Fixable CVEs in vaultwarden/server (3 critical, 17 high)[/-][+]Fixable CVEs in vaultwarden/server (0 critical, 1 high)[/+]Gerrrt commentedon Oct 10, 2026
Triage, 2026-10-10: nothing to change here. This waits on upstream.
1.37.4 is Vaultwarden's latest release, so there is no Dependabot bump yet. Upstream also hasn't rebuilt the tag:
docker buildx imagetools inspect vaultwarden/server:1.37.4still resolves to the pinnedsha256:efb3cde9….libselinux1, which comes in with the base userland (coreutils and friends)./vaultwardenbinary does not link pcre2 (ldd). Nothing on Vaultwarden's request path matches regexes through pcre2.The fix is a rebuild on an updated
debian:trixie-slim, either a rebuilt 1.37.4 digest or the next release.digests.ymlflags a rebuilt tag and Dependabot bumps a new release. The scan closes this issue when the digest comes back clean.To reproduce:
Gerrrt commentedon Oct 10, 2026
This is waiting on an upstream rebuild, the same as #990. Nothing in the repo needs to change.
sha256:efb3cde9…is the currentvaultwarden/server:1.37.4.pin-digests.shreports no drift, and Docker Hub has no newer release.libpcre2-8-0 10.46-1~deb13u3(DSA-6530-1), after that image was built.When upstream rebuilds 1.37.4 or ships 1.37.5+, Dependabot should open the digest bump. Check it with trivy and
check_image_pins.py, then deploy. The next scan will then close this issue.Gerrrt commentedon Oct 10, 2026
Rechecked 2026-10-10. Nothing has changed upstream: 1.37.4 is still the latest release, and
1.37.4/lateststill resolve to the pinnedsha256:efb3cde9….I also checked the alpine variant of the same release.
vaultwarden/server:1.37.4-alpine@sha256:19ea2b669945d842dadc3d500f2d6a795866a003330f59a47b9634658bae98bb(Alpine 3.24.2) scans clean with our pinned trivy (HIGH/CRITICAL, fixable). It ships/healthcheck.shandcurl, so the healthcheck would carry over.I'm still not switching. The finding is a base-image library that the
/vaultwardenbinary doesn't link. Changing the vault from the glibc build to the musl build means re-measuring everything the compose comments assert about the pinned image, including/dataownership and memory. That's more risk than waiting for Debian's rebuild. If upstream hasn't rebuilt by the next release, the alpine variant is the fallback.Gerrrt commentedon Oct 11, 2026
Request path, traced against the live container, 2026-10-11
I confirmed the triage above against the running
sensitive-vaultwardenon trinity. A fresh trivy 0.75.0 scan of1.37.4@sha256:efb3cde9…still shows the one HIGH, CVE-2026-103111 inlibpcre2-8-0, and it isn't reachable:/sbin/docker-init -- /start.shand/vaultwarden. The container isx86_64.libpcre2-8(checked in/proc/*/maps), so the library isn't even loaded.ldd /vaultwardenshows no pcre2 link (checked 2026-10-10), and on disk the only dependent islibselinux1.The decision above stands: wait for the Debian rebuild, with
1.37.4-alpineas the fallback.🤖 Traced by Claude Code
[-]Fixable CVEs in vaultwarden/server (0 critical, 1 high)[/-][+]Fixable CVEs in vaultwarden/server (0 critical, 7 high)[/+]github-actions commentedon Oct 19, 2026
New since the last scan: CVE-2026-8286, CVE-2026-8927, CVE-2026-92392.
[-]Fixable CVEs in vaultwarden/server (0 critical, 7 high)[/-][+]Fixable CVEs in vaultwarden/server (0 critical, 8 high)[/+]github-actions commentedon Oct 26, 2026
New since the last scan: CVE-2026-111497.
[-]Fixable CVEs in vaultwarden/server (0 critical, 8 high)[/-][+]Fixable CVEs in vaultwarden/server (1 critical, 7 high)[/+][-]Fixable CVEs in vaultwarden/server (1 critical, 7 high)[/-][+]Fixable CVEs in vaultwarden/server (1 critical, 11 high)[/+]github-actions commentedon Nov 9, 2026
New since the last scan: CVE-2026-109518, CVE-2026-76844, CVE-2026-85091.
[-]Fixable CVEs in vaultwarden/server (1 critical, 11 high)[/-][+]Fixable CVEs in vaultwarden/server (0 critical, 38 high)[/+]github-actions commentedon Nov 16, 2026
New since the last scan: CVE-2026-116304, CVE-2026-116306, CVE-2026-116307, CVE-2026-116309, CVE-2026-116314, CVE-2026-116315, CVE-2026-116316, CVE-2026-116317, CVE-2026-116319, CVE-2026-116320, CVE-2026-116323, CVE-2026-116325, CVE-2026-116326, CVE-2026-116328, CVE-2026-116330, CVE-2026-116331, CVE-2026-116332, CVE-2026-116335, CVE-2026-116336, CVE-2026-120139 and 14 more.