Skip to content

Fixable CVEs in valkey/valkey (0 critical, 3 high) #1006

Closed

Description

@github-actions

The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in valkey/valkey. 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.

valkey/valkey:9.1.2

Stacks: sensitive. Digest: sha256:418652cfb58ef879d4978c33553735d7147016032d5aefaa14c828e611eb9dfd.

Severity ID Package Installed Fixed in
HIGH CVE-2026-103111 libpcre2-8-0 10.46-1~deb13u2 10.46-1~deb13u3
HIGH CVE-2026-84782 libssl3t64 3.5.7-1~deb13u2 3.5.7-1~deb13u3
HIGH CVE-2026-84782 openssl-provider-legacy 3.5.7-1~deb13u2 3.5.7-1~deb13u3

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 valkey/valkey (0 critical, 5 high)[/-] [+]Fixable CVEs in valkey/valkey (0 critical, 3 high)[/+] on Oct 10, 2026
  3. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Triage, 2026-10-10: nothing to change here. This waits on upstream.

    The flagged pin is valkey/valkey:9.1.2, which serves immich-valkey only. paperless-broker runs 9.1.2-alpine, and the scan didn't flag it. 9.1.2 is the latest 9.1 release (9.2.0 is still at rc1), so there is no Dependabot bump yet. Docker Hub also hasn't rebuilt the tag: docker buildx imagetools inspect valkey/valkey:9.1.2 still resolves to the pinned sha256:418652cf….

    Finding Where it lives Reachable here?
    libssl3t64, openssl-provider-legacy 3.5.7-1~deb13u2 (CVE-2026-84782, fix ~deb13u3) Debian 13.7 base. valkey-server does link libssl.so.3/libcrypto.so.3, because the official build has TLS support. Low. TLS is off: immich-valkey has no command:, so there is no tls-port, and it only exposes plaintext 6379 on the stack network. Nothing is published to the host. The legacy provider is never loaded without an OpenSSL config asking for it.
    libpcre2-8-0 10.46-1~deb13u2 (CVE-2026-103111, fix ~deb13u3) Debian base, pulled in only by libselinux1. The same finding is open on #1007. No. valkey-server doesn't link pcre2.

    The fix is a rebuild on an updated debian:trixie-slim. Docker official images usually rebuild a tag soon after a Debian point update. When that happens, digests.yml flags the new digest, and the scan closes this issue once the repinned digest comes back clean. If it drags on, a fallback would be switching immich-valkey to the 9.1.2-alpine pin that paperless-broker already uses.

    To reproduce:

    IMG=valkey/valkey:9.1.2@sha256:418652cfb58ef879d4978c33553735d7147016032d5aefaa14c828e611eb9dfd
    docker run --rm --entrypoint sh "$IMG" -c 'ldd /usr/local/bin/valkey-server | grep -Ei "ssl|crypto|pcre"; awk "/^Package:/{p=\$2} /^Depends:.*(libssl3t64|libpcre2-8-0)/{print p}" /var/lib/dpkg/status'
  4. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    This is waiting on an upstream rebuild. Nothing in the repo needs to change.

    • The pinned digest sha256:418652cf… is the current valkey/valkey:9.1.2. pin-digests.sh reports no drift, and Docker Hub has no newer release.
    • All three findings are Debian base-layer packages, and Debian released both fixes after that image was built:
      • libpcre2-8-0 10.46-1~deb13u3 (DSA-6530-1)
      • libssl3t64 / openssl-provider-legacy 3.5.7-1~deb13u3 (DSA-6531-1)
    • The 9.1.2-alpine pin isn't listed here and isn't affected.

    When upstream rebuilds 9.1.2 or ships 9.1.3+, 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

    Fixed by #1147 (merged 2026-10-10 14:46 UTC). immich-valkey now runs valkey/valkey:9.1.2-alpine@sha256:48332870…, the same pin as paperless-broker, which the scan never flagged. Nothing in the repo pins the Debian valkey/valkey:9.1.2 digest any more.

    The change is deployed. On trinity at 15:45 UTC, sensitive-immich-valkey was running valkey/valkey:9.1.2-alpine and was healthy after its recreate.

    Leaving this open for the next scheduled scan, which will close it because the image is no longer pinned.

  6. github-actions commented on Oct 10, 2026

    @github-actions
    Author

    Clean at valkey/valkey:9.1.2-alpine@sha256:48332870af354a799964c0012ae1194a0bf2bf894eb508f945810596dc2d8d11: no fixable HIGH or CRITICAL findings. (scan)

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