Skip to content

Fixable CVEs in vaultwarden/server (0 critical, 38 high) #1007

Open

Description

@github-actions

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.

Activity

  1. added
    securityA credential, an exposure, or a control that is weaker than recorded
    sensitivestacks/sensitive on trinity (VLAN 99)
    on Oct 7, 2026
  2. changed the title [-]Fixable CVEs in vaultwarden/server (3 critical, 17 high)[/-] [+]Fixable CVEs in vaultwarden/server (0 critical, 1 high)[/+] on Oct 8, 2026
  3. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    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.4 still resolves to the pinned sha256:efb3cde9….

    Finding Where it lives Reachable here?
    libpcre2-8-0 10.46-1~deb13u2 (fix ~deb13u3) Debian 13.7 base-image package. Its only reverse dependency is libselinux1, which comes in with the base userland (coreutils and friends). Low. The /vaultwarden binary 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.yml flags a rebuilt tag and Dependabot bumps a new release. The scan closes this issue when the digest comes back clean.

    To reproduce:

    IMG=vaultwarden/server:1.37.4@sha256:efb3cde962015fcc036b2ea625242248611943b27212ebf4392841fb30fad055
    docker run --rm --entrypoint sh "$IMG" -c 'dpkg -s libpcre2-8-0 | grep Version; awk "/^Package:/{p=\$2} /^Depends:.*libpcre2-8-0/{print p}" /var/lib/dpkg/status; ldd /vaultwarden | grep -i pcre || echo no pcre'
  4. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    This is waiting on an upstream rebuild, the same as #990. Nothing in the repo needs to change.

    • The pinned digest sha256:efb3cde9… is the current vaultwarden/server:1.37.4. pin-digests.sh reports no drift, and Docker Hub has no newer release.
    • Debian released the fix, 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.

  5. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Rechecked 2026-10-10. Nothing has changed upstream: 1.37.4 is still the latest release, and 1.37.4 / latest still resolve to the pinned sha256: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.sh and curl, so the healthcheck would carry over.

    I'm still not switching. The finding is a base-image library that the /vaultwarden binary 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 /data ownership 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.

  6. Gerrrt commented on Oct 11, 2026

    @Gerrrt
    Owner

    Request path, traced against the live container, 2026-10-11

    I confirmed the triage above against the running sensitive-vaultwarden on trinity. A fresh trivy 0.75.0 scan of 1.37.4@sha256:efb3cde9… still shows the one HIGH, CVE-2026-103111 in libpcre2-8-0, and it isn't reachable:

    • What the bug needs: an attacker-controlled regular expression compiled and run through PCRE2's JIT API.
    • What runs: only /sbin/docker-init -- /start.sh and /vaultwarden. The container is x86_64.
    • No process maps libpcre2-8 (checked in /proc/*/maps), so the library isn't even loaded. ldd /vaultwarden shows no pcre2 link (checked 2026-10-10), and on disk the only dependent is libselinux1.

    The decision above stands: wait for the Debian rebuild, with 1.37.4-alpine as the fallback.

    docker exec sensitive-vaultwarden sh -c 'for p in /proc/[0-9]*; do grep -q pcre2 $p/maps 2>/dev/null && tr "\0" " " < $p/cmdline; done; echo end'

    🤖 Traced by Claude Code

  7. changed the title [-]Fixable CVEs in vaultwarden/server (0 critical, 1 high)[/-] [+]Fixable CVEs in vaultwarden/server (0 critical, 7 high)[/+] on Oct 19, 2026
  8. github-actions commented on Oct 19, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-8286, CVE-2026-8927, CVE-2026-92392.

  9. changed the title [-]Fixable CVEs in vaultwarden/server (0 critical, 7 high)[/-] [+]Fixable CVEs in vaultwarden/server (0 critical, 8 high)[/+] on Oct 26, 2026
  10. github-actions commented on Oct 26, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-111497.

  11. changed the title [-]Fixable CVEs in vaultwarden/server (0 critical, 8 high)[/-] [+]Fixable CVEs in vaultwarden/server (1 critical, 7 high)[/+] on Nov 2, 2026
  12. changed the title [-]Fixable CVEs in vaultwarden/server (1 critical, 7 high)[/-] [+]Fixable CVEs in vaultwarden/server (1 critical, 11 high)[/+] on Nov 9, 2026
  13. github-actions commented on Nov 9, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-109518, CVE-2026-76844, CVE-2026-85091.

  14. changed the title [-]Fixable CVEs in vaultwarden/server (1 critical, 11 high)[/-] [+]Fixable CVEs in vaultwarden/server (0 critical, 38 high)[/+] on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    securityA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions