CVE-2024-27304

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2024-03-04. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-0972 (ENISA EUVD) · GHSA-mrww-27vc-gghv (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 6, 2024

Last Modified

May 21, 2026

Advisory Details (7)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit, github.
GitHub commit Patch Available

commit adbb38f298c7 (jackc/pgx)

Patch available: jackc/pgx v5.11.0 (contains commit adbb38f298c7)

https://github.com/jackc/pgx/commit/adbb38f298c76e283ffc7c7a3f571036fea47fd4
GitHub advisoryMentions a patch (unverified)

SQL Injection via Protocol Message Size Overflow · Advisory · jackc/pgproto3 · GitHub

https://github.com/jackc/pgproto3/security/advisories/GHSA-7jwh-3vrq-q3m8
GitHub commit

commit 945c2126f6db (jackc/pgproto3)

Fix landed in jackc/pgproto3 commit 945c2126f6db — awaiting tagged release

https://github.com/jackc/pgproto3/commit/945c2126f6db8f3bea7eeebe307c01fe92bca007
GitHub advisoryMentions a patch (unverified)

SQL Injection via Protocol Message Size Overflow · Advisory · jackc/pgx · GitHub

https://github.com/jackc/pgx/security/advisories/GHSA-mrww-27vc-gghv
GitHub commit

commit f94eb0e2f967 (jackc/pgx)

Fix landed in jackc/pgx commit f94eb0e2f967 — awaiting tagged release

https://github.com/jackc/pgx/commit/f94eb0e2f96782042c96801b5ac448f44f0a81df
GitHub commit Patch Available

commit c543134753a0 (jackc/pgx)

Patch available: jackc/pgx v5.11.0 (contains commit c543134753a0)

https://github.com/jackc/pgx/commit/c543134753a0c5d22881c12404025724cb05ffd8

Vendor Advisories for CVE-2024-27304(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatadvanced-cluster-security/rhacs-scanner-slim-rhel8:4.3.5-32024-03-13redhat
gogithub.com/jackc/pgx @ 4.18.2 (fixes < 4.18.2)—ghsa
gogithub.com/jackc/pgx @ 5.5.4 (fixes >= 5.0.0, < 5.5.4)—ghsa

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

(12 across 5 ecosystems)
Go(5)
PackageVulnerable rangeFix by version rangeDependents
github.com/jackc/pgproto3—
  • every version up to 2.3.3: fixed in 2.3.3
—
github.com/jackc/pgproto3/v2—
  • every version up to 2.3.3: fixed in 2.3.3
—
github.com/jackc/pgx—
  • every version up to 4.18.2: fixed in 4.18.2
  • 5.0.0 up to 5.5.4: fixed in 5.5.4
  • every version on: no fix on record
—
github.com/jackc/pgx/v4—
  • every version up to 4.18.2: fixed in 4.18.2
—
github.com/jackc/pgx/v5—
  • 5.0.0 up to 5.5.4: fixed in 5.5.4
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-jackc-pgconn1.11.0-2, 1.14.0-1, 1.14.3-1, 1.14.3-1~exp0
  • every version on: no fix on record
—
golang-github-jackc-pgx4.15.0-4 ... 4.18.3-2 (6 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-jackc-pgconn1.14.0-1, 1.14.3-1, 1.14.3-1~exp0
  • every version on: no fix on record
—
golang-github-jackc-pgx—
  • every version up to 4.18.1-2: fixed in 4.18.1-2
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
golang-github-jackc-pgconn1.14.0-1, 1.14.3-1~exp0
  • every version up to 1.14.3-1: fixed in 1.14.3-1
—
golang-github-jackc-pgx—
  • every version up to 4.18.1-2: fixed in 4.18.1-2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-jackc-pgx3.6.2-2 ... 4.18.3-2 (10 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 79× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 264 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 167 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-03 00:22 UTCEG score recompute
  2. 2026-11-03 00:22 UTCVendor advisory
  3. 2026-11-03 00:22 UTCGHSA enrichmentGHSA-mrww-27vc-gghv · GitHub severity HIGH · GitHub CVSS 9.8
  4. 2026-11-02 16:40 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-11-01 23:04 UTCEG score recompute
  6. 2026-11-01 23:04 UTCVendor advisory
  7. 2026-11-01 23:04 UTCGHSA enrichmentGHSA-mrww-27vc-gghv · GitHub severity HIGH · GitHub CVSS 9.8
  8. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  9. 2026-11-01 08:15 UTCGHSA enrichmentGHSA-mrww-27vc-gghv · GitHub severity HIGH · GitHub CVSS 9.8
  10. 2026-11-01 08:15 UTCEG score recompute
  11. 2026-10-31 21:45 UTCEG score recompute
  12. 2026-10-31 21:45 UTCVendor advisory
  13. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-30 20:27 UTCEG score recompute
  15. 2026-10-30 20:27 UTCVendor advisory
  16. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  17. 2026-10-29 19:09 UTCEG score recompute
  18. 2026-10-29 19:09 UTCVendor advisory
  19. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-10-28 17:51 UTCEG score recompute
  21. 2026-10-28 17:51 UTCVendor advisory
  22. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  23. 2026-10-27 16:33 UTCEG score recompute
  24. 2026-10-27 16:33 UTCVendor advisory
  25. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
Show 72 more
  1. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  2. 2026-10-26 15:11 UTCVendor advisory
  3. 2026-10-25 17:15 UTCEG score recompute
  4. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  5. 2026-10-25 12:51 UTCEG score recompute
  6. 2026-10-25 12:51 UTCVendor advisory
  7. 2026-10-24 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  8. 2026-10-24 11:33 UTCEG score recompute
  9. 2026-10-24 11:33 UTCVendor advisory
  10. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  11. 2026-10-23 10:15 UTCEG score recompute
  12. 2026-10-23 10:15 UTCVendor advisory
  13. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  14. 2026-10-22 08:52 UTCEG score recompute
  15. 2026-10-22 08:52 UTCVendor advisory
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  17. 2026-10-21 07:33 UTCEG score recompute
  18. 2026-10-21 07:33 UTCVendor advisory
  19. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  20. 2026-10-20 06:15 UTCEG score recompute
  21. 2026-10-20 06:15 UTCVendor advisory
  22. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  23. 2026-10-19 04:56 UTCEG score recompute
  24. 2026-10-19 04:56 UTCVendor advisory
  25. 2026-10-18 16:29 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  26. 2026-10-18 03:36 UTCEG score recompute
  27. 2026-10-18 03:36 UTCVendor advisory
  28. 2026-10-17 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  29. 2026-10-17 02:16 UTCEG score recompute
  30. 2026-10-17 02:16 UTCVendor advisory
  31. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  32. 2026-10-16 00:53 UTCEG score recompute
  33. 2026-10-16 00:53 UTCVendor advisory
  34. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  35. 2026-10-14 19:49 UTCEG score recompute
  36. 2026-10-14 19:49 UTCVendor advisory
  37. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  38. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.1% · 65th percentile
  39. 2026-10-13 15:59 UTCEG score recompute
  40. 2026-10-13 15:59 UTCVendor advisory
  41. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  42. 2026-10-12 14:40 UTCEG score recompute
  43. 2026-10-12 14:40 UTCVendor advisory
  44. 2026-10-11 21:23 UTCEG score recompute
  45. 2026-10-11 16:17 UTCEG score recompute
  46. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  47. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  48. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  49. 2026-10-08 17:07 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  50. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  51. 2026-10-07 16:05 UTCOSV refresh
  52. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  53. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  54. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  55. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  56. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  57. 2026-09-30 17:00 UTCEG score recompute
  58. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  59. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  60. 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  61. 2026-09-27 13:43 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  62. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  63. 2026-09-26 00:23 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  64. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  65. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  66. 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  67. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  68. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  69. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  70. 2026-09-17 22:20 UTCOSV refresh
  71. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.1% · 64th percentile
  72. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.1% · 64th percentile

Frequently asked(5)

What is CVE-2024-27304?
CVE-2024-27304 is a critical-severity vulnerability; its CVE record was published on March 6, 2024. 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…
When was the CVE record for CVE-2024-27304 published?
The CVE record for CVE-2024-27304 was published on March 6, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 21, 2026; the record at its source may have been updated since.
Is CVE-2024-27304 actively exploited?
CVE-2024-27304 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-27304?
CVE-2024-27304 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-27304?
A fix for CVE-2024-27304 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-27304 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-27304

Explore →

Is Your Infrastructure Affected by CVE-2024-27304?

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