CVE-2026-33815

criticalpriority · track · 0EPSS 0.009 · 58 %ileEUUS

grimoire priorityP2 · Scheduled

Exploitable?

—

no known exploitation

Likely / severe?

0.86% (58th) EPSS

CVSS 9.8 · critical

Is it mine?

3 products

Who says so?

4 sources

cnnvd · enisa_euvd · osv · nvd

EPSS · scored 2026-10-23

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

cvss

Technical severity, 0–10. One row per scoring source.

9.8

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · high–critical · 8.3–9.8

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · ENISA EU

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondaryexploitability 3.9 · impact 5.9

v3.18.3highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Lsecondaryexploitability 2.8 · impact 5.5

v3.19.8criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsecondary · OSV

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: yes · Technical Impact: totalcoordinatorcisa_ssvcUS

The CWE weakness classes this flaw belongs to.

Products and version ranges known to be affected.

Vendor and ecosystem advisories describing this.

GHSA-xgrm-4fwx-7qm8pgx contains memory-safety vulnerability2026-04-07ghsa · osvUS
[pgx](github.com/jackc/pgx/v5) is a pure Go driver and toolkit for PostgreSQL. pgx prior to v5.9.0 contains a memory-safety vulnerability.
GO-2026-4771CVE-2026-33815 in github.com/jackc/pgx2026-04-07vendor · osvUS
Memory-safety vulnerability in github.com/jackc/pgx/v5.

Other names and identifiers for this entity.

Which sources assert this record, and when.

published 2026-04-07modified 2026-09-10

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.