home / Postgres / postgres:17.11-bookworm docker pull postgres:17.11-bookworm click to select
Image metadata PULL COUNT
12.0B
repository-level (not per-tag)
RUNS AS
root
image config.User
LAST PUSHED
15d ago
2026-10-06 07:10:16
MANIFEST DIGEST
sha256:3645570cccdf…
from registry manifest
Latest scan 2026-10-13 12:21:29 UTC · 8d ago OPEN CVES BY SEVERITY
Grype DB 2026-10-11T06:30:42.000Z
· rubric cerodeo-v1
RUBRIC BREAKDOWN (8 signals that moved the score) -75 · Critical CVEs (fixable) -310 · High CVEs (fixable) -63 · Medium CVEs (fixable) -64 · Critical CVEs (no fix) -261 · High CVEs (no fix) +10 · Rebuilt in last 90 days +3 · Multi-arch +2 · readme_has_example
Raw data
Every signal above decomposes to arithmetic from inputs you can verify. Nothing in these downloads is derived or
massaged — they're the raw grype matches and the raw snapshot history exactly as our scanner wrote them.
Reproduce this score yourself
We don't use judgement to score — every signal is deterministic from the image, the manifest, and a pinned CVE DB.
Run the script below on any host with skopeo, syft,
grype, cosign, and jq installed — it fetches the versioned rubric spec, computes the same breakdown, and prints the same grade. Pin the Grype DB with --grype-db to reproduce bit-for-bit identical results.
curl -fsSLO https://ce.rodeo/verify-score.sh && chmod +x verify-score.sh
./verify-score.sh postgres:17.11-bookworm \
--rubric cerodeo-v1 \
--grype-db 2026-10-11T06:30:42.000Z
All open CVEs (466) sorted by severity, then CVSS score CVE ID SEV CVSS PACKAGE FIX
CVE-2026-5450 CRITICAL 9.8 libc-l10n 2.36-9+deb12u14 no fix available CVE-2026-5450 CRITICAL 9.8 locales 2.36-9+deb12u14 no fix available CVE-2026-5450 CRITICAL 9.8 libc6 2.36-9+deb12u14 no fix available CVE-2026-5450 CRITICAL 9.8 libc-bin 2.36-9+deb12u14 no fix available CVE-2026-6653 CRITICAL 9.8 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2025-7458 CRITICAL 9.1 libsqlite3-0 3.40.1-2+deb12u2 no fix available CVE-2026-88647 CRITICAL 9.1 libgnutls30 3.7.9-2+deb12u7 no fix available CVE-2026-95210 CRITICAL 9.1 libgnutls30 3.7.9-2+deb12u7 no fix available CVE-2026-11822 HIGH 8.5 libsqlite3-0 3.40.1-2+deb12u2 no fix available CVE-2026-11824 HIGH 8.5 libsqlite3-0 3.40.1-2+deb12u2 no fix available CVE-2026-74860 HIGH 8.5 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-76642 HIGH 8.5 util-linux-extra 2.38.1-5+deb12u3 no fix available CVE-2026-76642 HIGH 8.5 libsmartcols1 2.38.1-5+deb12u3 no fix available CVE-2026-78408 HIGH 7.9 util-linux-extra 2.38.1-5+deb12u3 no fix available CVE-2026-78408 HIGH 7.9 libsmartcols1 2.38.1-5+deb12u3 no fix available CVE-2026-78410 HIGH 7.8 util-linux-extra 2.38.1-5+deb12u3 no fix available CVE-2026-78410 HIGH 7.8 libsmartcols1 2.38.1-5+deb12u3 no fix available CVE-2026-86138 HIGH 7.8 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-86140 HIGH 7.8 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-86142 HIGH 7.8 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-86144 HIGH 7.8 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-95619 HIGH 7.7 gcc-12-base 12.2.0-14+deb12u1 no fix available CVE-2023-2953 HIGH 7.5 libldap-2.5-0 2.5.13+dfsg-5 no fix available CVE-2026-107161 HIGH 7.5 libsasl2-modules-db 2.1.28+dfsg-10 no fix available CVE-2026-5928 HIGH 7.5 libc-l10n 2.36-9+deb12u14 no fix available CVE-2026-82560 HIGH 7.5 perl-modules-5.36 5.36.0-7+deb12u4 no fix available CVE-2026-9538 HIGH 7.5 perl-base 5.36.0-7+deb12u4 no fix available CVE-2026-9538 HIGH 7.5 perl-modules-5.36 5.36.0-7+deb12u4 no fix available CVE-2026-9538 HIGH 7.5 libperl5.36 5.36.0-7+deb12u4 no fix available CVE-2026-5435 HIGH 7.3 libc-l10n 2.36-9+deb12u14 no fix available CVE-2026-86143 HIGH 7.3 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-107778 HIGH 7.1 libgssapi-krb5-2 1.20.1-2+deb12u5 no fix available CVE-2026-78409 HIGH 7.0 util-linux-extra 2.38.1-5+deb12u3 no fix available CVE-2026-78409 HIGH 7.0 libsmartcols1 2.38.1-5+deb12u3 no fix available CVE-2025-7709 MEDIUM 6.9 libsqlite3-0 3.40.1-2+deb12u2 no fix available CVE-2026-54411 MEDIUM 6.9 libpam-runtime 1.5.2-6+deb12u2 no fix available CVE-2026-54411 MEDIUM 6.9 libpam-modules-bin 1.5.2-6+deb12u2 no fix available CVE-2026-54411 MEDIUM 6.9 libpam-modules 1.5.2-6+deb12u2 no fix available CVE-2026-16742 MEDIUM 6.7 libsystemd0 252.39-1~deb12u2 no fix available CVE-2026-6791 MEDIUM 6.6 libc-bin 2.36-9+deb12u14 no fix available CVE-2026-6791 MEDIUM 6.6 libc-l10n 2.36-9+deb12u14 no fix available CVE-2026-6791 MEDIUM 6.6 locales 2.36-9+deb12u14 no fix available CVE-2026-6238 MEDIUM 6.5 libc-bin 2.36-9+deb12u14 no fix available CVE-2026-6238 MEDIUM 6.5 libc-l10n 2.36-9+deb12u14 no fix available CVE-2026-6238 MEDIUM 6.5 locales 2.36-9+deb12u14 no fix available CVE-2026-15534 MEDIUM 5.7 libperl5.36 5.36.0-7+deb12u4 no fix available CVE-2026-15534 MEDIUM 5.7 perl-modules-5.36 5.36.0-7+deb12u4 no fix available CVE-2025-10911 MEDIUM 5.5 libxslt1.1 1.1.35-1+deb12u4 no fix available CVE-2026-15059 MEDIUM 5.5 libsystemd0 252.39-1~deb12u2 no fix available CVE-2026-50812 MEDIUM 5.5 libsqlite3-0 3.40.1-2+deb12u2 no fix available CVE-2026-50813 MEDIUM 5.5 libsqlite3-0 3.40.1-2+deb12u2 no fix available CVE-2026-5704 MEDIUM 5.5 tar 1.34+dfsg-1.2+deb12u1 no fix available CVE-2026-76781 MEDIUM 5.5 libxml2 2.9.14+dfsg-1.3~deb12u6 no fix available CVE-2026-13595 MEDIUM 5.3 util-linux 2.38.1-5+deb12u3 no fix available CVE-2026-13595 MEDIUM 5.3 libsmartcols1 2.38.1-5+deb12u3 no fix available CVE-2026-13595 MEDIUM 5.3 bsdutils 1:2.38.1-5+deb12u3 no fix available CVE-2026-13595 MEDIUM 5.3 util-linux-extra 2.38.1-5+deb12u3 no fix available CVE-2026-3184 MEDIUM 5.3 util-linux-extra 2.38.1-5+deb12u3 no fix available
Scan history 2 total · first 9d ago SCANNED AT GRADE SCORE CRIT HIGH MED GRYPE DB
8d ago F 0 11 118 151 2026-10-11T06:30:42.000Z · (same SBOM)
9d ago F 0 11 118 151 2026-10-11T06:30:42.000Z
Methodology:
This image is re-matched against the fresh Grype vulnerability DB every hour. Snapshot rows marked
(same SBOM) reuse the prior scan's content via a pointer — about
90% of hourly cycles do. New CVE disclosures land in a new content row and bump the grade on the next match.
Full rubric at /about/grades ; for publishers wanting to
raise their grade, see /about/for-publishers .
Discussion
No comments yet. Be the first.