Security Digest · Vulnerability record

CVE-2026-33815: pgx contains memory-safety vulnerability

Memory-safety vulnerability in github.com/jackc/pgx/v5.

CVSS 8.3 High EPSS 0.9% · p58

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.9%, percentile 58: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 58% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Needs an account (low (any account)). Exposure depends on who can log in.
  • Only applies if your dependency tree includes github.com/jackc/pgx/v5 (Go) < 5.9.0, fixed in 5.9.0. Check your lockfile, including transitive dependencies.

What it is

Memory-safety vulnerability in github.com/jackc/pgx/v5.

From the GitHub advisory

pgx is a pure Go driver and toolkit for PostgreSQL. pgx prior to v5.9.0 contains a memory-safety vulnerability.

Weakness type: CWE-787.

Product: github.com/jackc/pgx/v5 (Go) · Assigned by: Go · Published: 2026-04-07

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Gogithub.com/jackc/pgx/v5< 5.9.05.9.0
VendorProductAffected versions (per CVE record)
github.com/jackc/pgx/v5github.com/jackc/pgx/v5/pgproto3< 5.9.0

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
redhat-SADP3.18.3 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
GitHub3.19.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: low (any account)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.86% probability of exploitation activity in the next 30 days; percentile 58.

Timeline

  • — CVE record published by Go
  • — GitHub-reviewed advisory GHSA-xgrm-4fwx-7qm8 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. access.redhat.com access.redhat.com
  2. access.redhat.com access.redhat.com
  3. access.redhat.com access.redhat.com
  4. access.redhat.com access.redhat.com
  5. access.redhat.com access.redhat.com
  6. access.redhat.com access.redhat.com
  7. access.redhat.com access.redhat.com
  8. access.redhat.com access.redhat.com
  9. access.redhat.com access.redhat.com
  10. access.redhat.com access.redhat.com
  11. access.redhat.com access.redhat.com
  12. access.redhat.com access.redhat.com
  13. access.redhat.com access.redhat.com
  14. access.redhat.com access.redhat.com
  15. access.redhat.com access.redhat.com
  16. access.redhat.com access.redhat.com
  17. access.redhat.com access.redhat.com

Vulnerability records

  1. GitHub Advisory GHSA-xgrm-4fwx-7qm8 github.com
  2. CVE.org record CVE-2026-33815 cve.org
  3. NVD entry CVE-2026-33815 nvd.nist.gov

Other references from the CVE record and advisory

  1. pkg.go.dev pkg.go.dev
  2. access.redhat.com access.redhat.com
  3. RHBZ#2455975 bugzilla.redhat.com
  4. security.access.redhat.com security.access.redhat.com
  5. github.com github.com
  6. github.com github.com
  7. github.com github.com

Critical Go advisories · Today’s Security Digest