CVE-2026-33815

CRITICALNVD 9.89.8—

9.8

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

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 6.4%
KEV: Not listed

Published

April 7, 2026

Last Modified

May 21, 2026

Advisory Details (1)

Auto-updated May 18, 2026

No patch confirmed yet.

generic

GO-2026-4771 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4771

Vendor Advisories for CVE-2026-33815(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
redhat	advanced-cluster-security/rhacs-scanner-v4-rhel8:1777986630	2026-05-05	redhat
redhat	advanced-cluster-security/rhacs-scanner-v4-rhel8:1777976489	2026-05-05	redhat
redhat	advanced-cluster-security/rhacs-scanner-v4-rhel8:1777307791	2026-04-27	redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)

Go(2)

Package	Vulnerable range	Fixed in	Dependents
github.com/jackc/pgx/v5	—	5.9.0	—
github.com/jackc/pgx/v5/pgproto3	—	5.9.0	—

Data Freshness Timeline

(refreshed 7× in last 7d / 13× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:44 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-23 00:08 UTCEG score recompute
2026-05-20 22:38 UTCepss_batch
2026-05-20 22:38 UTCepss_batch
2026-05-20 18:43 UTCEG score recompute
2026-05-20 18:43 UTCVendor advisory
2026-05-20 11:22 UTCepss_batch
2026-05-20 11:22 UTCepss_batch

Frequently asked(5)

What is CVE-2026-33815?

CVE-2026-33815 is a critical vulnerability published on April 7, 2026. Memory-safety vulnerability in github.com/jackc/pgx/v5.

When was CVE-2026-33815 disclosed?

CVE-2026-33815 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on May 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-33815 actively exploited?

CVE-2026-33815 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-33815?

CVE-2026-33815 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2026-33815?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33815, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33815

Explore →

Is Your Infrastructure Affected by CVE-2026-33815?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs