Memory-safety flaw in Go pgx pgproto3 component
CVE-2026-33816 Published on April 7, 2026
CVE-2026-33816 in github.com/jackc/pgx
Memory-safety vulnerability in github.com/jackc/pgx/v5.
Vulnerability Analysis
CVE-2026-33816 is exploitable with network access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality and integrity, and a small impact on availability.
Weakness Type
What is a Memory Corruption Vulnerability?
The software writes data past the end, or before the beginning, of the intended buffer. Typically, this can result in corruption of data, a crash, or code execution. The software may modify an index or perform pointer arithmetic that references a memory location that is outside of the boundaries of the buffer. A subsequent write operation then produces undefined or unexpected results.
CVE-2026-33816 has been classified to as a Memory Corruption vulnerability or weakness.
Products Associated with CVE-2026-33816
Want to know whenever a new CVE is published for Red Hat products? stack.watch will email you.
Affected Versions
github.com/jackc/pgx/v5/pgproto3:- Before 5.9.0 is affected.
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.