Skip to content

Fixable CVEs in postgres (0 critical, 72 high) #1335

Open

Description

@github-actions

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

postgres:17.11

Stacks: wiki. Digest: sha256:ff87138949ad9a46f32ff23bd6852b52ce024a13dffe9b4087be98292cdd3b4f.

Severity ID Package Installed Fixed in
HIGH CVE-2026-116304 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116306 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116307 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116309 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116314 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116315 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116316 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116317 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116319 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116320 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116323 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116325 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116326 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116328 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116330 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116331 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116332 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116335 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116336 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120139 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120141 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120142 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120143 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120145 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120147 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120148 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120149 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120150 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120151 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120153 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-14661 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-18447 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-6460 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-6467 postgresql-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116304 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116306 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116307 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116309 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116314 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116315 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116316 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116317 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116319 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116320 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116323 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116325 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116326 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116328 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116330 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116331 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116332 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116335 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-116336 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120139 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120141 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120142 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120143 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120145 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120147 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120148 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120149 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120150 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120151 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-120153 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-14661 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-18447 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-6460 postgresql-client-17 17.11-1.pgdg13+2 17.12-0+deb13u1
HIGH CVE-2026-6467 postgresql-client-17 17.11-1.pgdg13+2 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

postgres:18.6

Stacks: bloodhound, sensitive. Digest: sha256:e3d24f6906d0760bf4da0dae872415391ededefad23fd471c47dc53b0ddf3c42.

Severity ID Package Installed Fixed in
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)
    wikistacks/wiki on oracle (VLAN 99)
    bloodhoundstacks/bloodhound on eden (VLAN 30)
    on Nov 9, 2026
  2. changed the title [-]Fixable CVEs in postgres (0 critical, 8 high)[/-] [+]Fixable CVEs in postgres (0 critical, 72 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

    bloodhoundstacks/bloodhound on eden (VLAN 30)securityA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)wikistacks/wiki on oracle (VLAN 99)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions