CVE-2026-33816: Memory-safety vulnerability in github.com/jackc/pgx/v5.
CVE-2026-33816 is a critical-severity flaw (CVSS 9.8) affecting pgx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Memory-safety vulnerability in github.com/jackc/pgx/v5.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 54%) |
| CISA exploited list | No |
| Weakness | CWE-787 |
| Published | 2026-04-07 |
| Last modified | 2026-10-26 |
Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-33816?
pgx: upgrade to 5.9.0. Exact commands for each OS are on this page.
Is CVE-2026-33816 being exploited?
CVE-2026-33816 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-33816 affect?
CVE-2026-33816 affects pgx. Severity is critical (CVSS 9.8). Memory-safety vulnerability in github.com/jackc/pgx/v5.
How urgent is CVE-2026-33816?
Priority 51/100. Critical severity; Remotely exploitable, no login, no user action
Software pages
Related CVEs
- CVE-2026-33815 CRITICAL 9.8 MITIGATE 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