CVE-2026-33815
Memory-safety bug in pgx/v5 driver could cause memory corruption.
Is CVE-2026-33815 being exploited?
Not confirmed. CVE-2026-33815 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.60% probability of exploitation in the next 30 days.
How severe is CVE-2026-33815?
CVE-2026-33815 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-33815?
Yes. A fix has been recorded for CVE-2026-33815. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33815 affect?
CVE-2026-33815 affects github.com/jackc/pgx/v5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33815?
Upgrade to patched pgx/v5 release when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory corruption in Go process using pgx/v5; could crash or destabilize the service.
Immediate action required
- affected< 5.9.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.