pgx vulnerabilities and fixes

Recent CVEs affecting pgx, with upgrade or downgrade steps. 3 tracked.

pgx has 3 tracked vulnerabilities, 3 critical. A fixed release or vendor patch exists for 2. Most recent: 2026-05-08. Highest priority: CVE-2026-33815 (score 51/100).

• CVE-2026-33815 CRITICAL 9.8 MITIGATE Memory-safety vulnerability in github.com/jackc/pgx/v5.
• CVE-2026-33816 CRITICAL 9.8 UPGRADE Memory-safety vulnerability in github.com/jackc/pgx/v5.
• CVE-2026-41889 CRITICAL 9.8 UPGRADE pgx is a PostgreSQL driver and toolkit for Go

FAQ

How do I fix pgx vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is pgx being exploited right now?

None of the tracked pgx CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which pgx CVE should I patch first?

CVE-2026-33815 currently ranks highest (51/100): Memory-safety vulnerability in github.com/jackc/pgx/v5..

RSS feed for pgx · ← Back to latest CVEs