Skip to content

fix: cve-2026-33815 and cve-2026-33816 in pgx#8

Closed
vmrh21 wants to merge 1 commit intomainfrom
fix/cve-2026-33815-pgx-rhds-main-attempt-2
Closed

fix: cve-2026-33815 and cve-2026-33816 in pgx#8
vmrh21 wants to merge 1 commit intomainfrom
fix/cve-2026-33815-pgx-rhds-main-attempt-2

Conversation

@vmrh21
Copy link
Copy Markdown
Owner

@vmrh21 vmrh21 commented Apr 21, 2026

summary

update github.com/jackc/pgx/v5 from v5.7.6 to v5.9.2 to resolve memory-safety vulnerabilities.

cve details

changes

  • updated github.com/jackc/pgx/v5 from v5.7.6 to v5.9.2 in maas-api/go.mod
  • ran go mod tidy to update go.sum

test results

status: ✅ all tests passed
command: go test ./...

jira

  • resolves: rhoaieng-57067
  • resolves: rhoaieng-57063

🤖 generated with claude code

update github.com/jackc/pgx/v5 from v5.7.6 to v5.9.2 to resolve
memory-safety vulnerabilities.

cve details:
- cve-2026-33815: memory-safety vulnerability in pgx
- cve-2026-33816: memory-safety vulnerability in pgx

resolves: rhoaieng-57067, rhoaieng-57063

co-authored-by: claude opus 4.6 <noreply@anthropic.com>
@vmrh21 vmrh21 closed this Apr 21, 2026
@vmrh21 vmrh21 deleted the fix/cve-2026-33815-pgx-rhds-main-attempt-2 branch April 21, 2026 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant