CVE-2024-27304 | pgx SQL Injection via Protocol Message Size Overflow

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.

Published: 2024-03-06 Last update: 2026-05-21 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-27304 is rated High Risk (68.7/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.88%). High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-27304

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-25 1.39% 1.88% +0.48%
2 2026-03-12 2.17% 1.39% -0.78%
3 2025-12-24 — 2.17% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-27304

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2024-27304

GitHub Security Advisory for CVE-2024-27304

GHSA-mrww-27vc-gghv · Severity: high · Ecosystem: go — pgx SQL Injection via Protocol Message Size Overflow

OS Trackers for CVE-2024-27304

vendor priority summary link
debian not yet assigned CVE-2024-27304 not yet assigned priority: Debian including 2 source packages (golang-github-jackc-pgconn, golang-github-jackc-pgx), 9 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5, open 4. https://security-tracker.debian.org/tracker/CVE-2024-27304
redhat medium — https://access.redhat.com/security/cve/CVE-2024-27304
ubuntu medium CVE-2024-27304 medium priority: Ubuntu including 2 source packages (golang-github-jackc-pgproto3, golang-github-jackc-pgx), 16 status rows across 8 suites (focal, jammy, mantic, noble, oracular, plucky, questing, upstream): needs-triage 7, ignored 6, DNE 3. https://ubuntu.com/security/CVE-2024-27304

Affected software / configurations for CVE-2024-27304

Vendor Product Version Raw CPE
jackc pgproto3 < 2.3.3 cpe:2.3:a:jackc:pgproto3:*:*:*:*:*:go:*:*
jackc pgx < 4.18.2 cpe:2.3:a:jackc:pgx:*:*:*:*:*:go:*:*
jackc pgx >= 5.0.0, < 5.5.4 cpe:2.3:a:jackc:pgx:*:*:*:*:*:go:*:*

References for CVE-2024-27304

cvelogic Threat Intelligence