This page lists publicly disclosed CVE vulnerabilities affecting jackc pgx (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-41889 | pgx is a PostgreSQL driver and toolkit for Go. Prior to version 5.9.2, SQL injection can occur when the non-default simple protocol is used, a dollar quoted string literal is used in the SQL query, that string literal contains text that would be would be interpreted as a placeholder outside of a string literal, and the value of that placeholder is controllable by the attacker. This issue has been patched in version 5.9.2. | [email protected] | 2.3 | 0.01% | 2026-05-08 | 2026-05-21 |
| CVE-2026-33816 | Memory-safety vulnerability in github.com/jackc/pgx/v5. | [email protected] | 9.8 | 0.02% | 2026-04-07 | 2026-05-21 |
| CVE-2026-33815 | Memory-safety vulnerability in github.com/jackc/pgx/v5. | [email protected] | 9.8 | 0.02% | 2026-04-07 | 2026-05-21 |
| CVE-2024-27304 | pgx is a PostgreSQL driver and toolkit for Go. SQL injection can occur if an attacker can cause a single query or bind message to exceed 4 GB in size. An integer overflow in the calculated message size can cause the one large message to be sent as multiple messages under the attacker's control. The problem is resolved in v4.18.2 and v5.5.4. As a workaround, reject user input large enough to cause a single query or bind message to exceed 4 GB in size. | [email protected] | 9.8 | 1.88% | 2024-03-06 | 2026-05-21 |
| CVE-2024-27289 | pgx is a PostgreSQL driver and toolkit for Go. Prior to version 4.18.2, SQL injection can occur when all of the following conditions are met: the non-default simple protocol is used; a placeholder for a numeric value must be immediately preceded by a minus; there must be a second placeholder for a string value after the first placeholder; both must be on the same line; and both parameter values must be user-controlled. The problem is resolved in v4.18.2. As a workaround, do not use the simple pr | [email protected] | 8.1 | 0.59% | 2024-03-06 | 2026-05-21 |