From: iniTwakkie (@iniTwakkie) <noreply+iniTwakkie@github.com>
To: pgvector/pgvector <noreply+pgvector-pgvector@github.com>
Subject: [pgvector/pgvector] issue #1050: Rebuild pg16 image for Debian Perl and Go stdlib security fixes
Date: Sat, 31 Oct 2026 08:36:12 +0000
Message-ID: <gh-pgvector-pgvector-1050@github.com> (raw)
### Summary
The current `pgvector/pgvector:pg16` image reports critical findings that come from its base image rather than the extension:
- `perl`, `perl-base`, `perl-modules-5.36`, `libperl5.36` at `5.36.0-7+deb12u3` → `5.36.0-7+deb12u4` (CVE-2026-13221, CVE-2026-42496, CVE-2026-8376)
- Go `stdlib` 1.24.6 → 1.24.13 in `gosu` (CVE-2025-68121)
This is not a pgvector code issue. The Dockerfile builds on `postgres:16-bookworm`, and a rebuild against the current base should pick up the fixed Debian packages and `gosu`.
### Reproduction
```bash
trivy image --scanners vuln --severity HIGH,CRITICAL --ignore-unfixed pgvector/pgvector:pg16
```
### Request
Could the `pg16` image be rebuilt against the current `postgres:16-bookworm` base? If the base image still carries the same packages, a short note on the expected upstream fix would be helpful.
I am not asking for a code change here — this is an image rebuild request.