chore(deps): bump github.com/jackc/pgx/v5 to v5.9.0#1936
Merged
piotrjanik merged 1 commit intoMay 4, 2026
Merged
Conversation
#### What this PR does / why we need it Bumps `github.com/jackc/pgx/v5` from v5.8.0 to v5.9.0 to address CVE-2026-33815 (GHSA-xgrm-4fwx-7qm8), a memory-safety vulnerability in `pgproto3.Backend.Receive` and `Bind.Decode` (CVSS 9.8). Fixed upstream in v5.9.0. pgx is an indirect dependency only — pulled in via cosign → sigstore-go → certificate-transparency-go's optional postgresql storage backend. No package in this repo imports pgx, so the vulnerable symbols are not reachable at runtime; the bump is to satisfy SCA scanners. #### Which issue(s) this PR fixes Fixes: CVE-2026-33815 / GHSA-xgrm-4fwx-7qm8 Signed-off-by: Piotr Janik <piotr.janik@sap.com>
morri-son
approved these changes
May 4, 2026
Skarlso
approved these changes
May 4, 2026
piotrjanik
added a commit
to piotrjanik/ocm
that referenced
this pull request
May 4, 2026
…odel#1936) Bumps `github.com/jackc/pgx/v5` from v5.8.0 to v5.9.0 to address CVE-2026-33815 (GHSA-xgrm-4fwx-7qm8), a memory-safety vulnerability in `pgproto3.Backend.Receive` and `Bind.Decode` (CVSS 9.8). Fixed upstream in v5.9.0. pgx is an indirect dependency only — pulled in via cosign → sigstore-go → certificate-transparency-go's optional postgresql storage backend. Fixes: CVE-2026-33815 / GHSA-xgrm-4fwx-7qm8 <!-- markdownlint-disable MD041 --> <!-- Usage: `Related to #<issue number>`, or `Related to (paste link of issue)`. --> Signed-off-by: Piotr Janik <piotr.janik@sap.com>
piotrjanik
added a commit
that referenced
this pull request
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
Bumps
github.com/jackc/pgx/v5from v5.8.0 to v5.9.0 to address CVE-2026-33815 (GHSA-xgrm-4fwx-7qm8), a memory-safety vulnerability inpgproto3.Backend.ReceiveandBind.Decode(CVSS 9.8). Fixed upstream in v5.9.0.pgx is an indirect dependency only — pulled in via cosign → sigstore-go → certificate-transparency-go's optional postgresql storage backend.
Which issue(s) this PR fixes
Fixes: CVE-2026-33815 / GHSA-xgrm-4fwx-7qm8
What this PR does / why we need it
Which issue(s) this PR is related to