CVE-2024-32655

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 1.7%, top 25% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Npgsql is the .NET data provider for PostgreSQL. The WriteBind() method in src/Npgsql/Internal/NpgsqlConnector.FrontendMessages.cs uses int variables to store the message length and the sum of parameter lengths. Both variables overflow when the sum of parameter lengths becomes too large. This causes Npgsql to write a message size that is too small when constructing a Postgres protocol message to send it over the network to the database. When parsing the message, the database will only read a small number of bytes and treat any following bytes as new messages while they belong to the old message. Attackers can abuse this to inject arbitrary Postgres protocol messages into the connection, leading to the execution of arbitrary SQL statements on the application's behalf. This vulnerability is fixed in 4.0.14, 4.1.13, 5.0.18, 6.0.11, 7.0.7, and 8.0.3.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
76%
KEV
Not listed

Published

May 14, 2024

Last Modified

April 15, 2026

Advisory Details (10)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release, github_commit.
github_release Patch Available

v5.0.18

Patch available: npgsql/npgsql v5.0.18

https://github.com/npgsql/npgsql/releases/tag/v5.0.18
github_release Patch Available

v4.1.13

Patch available: npgsql/npgsql v4.1.13

https://github.com/npgsql/npgsql/releases/tag/v4.1.13
github_release Patch Available

v4.0.14

Patch available: npgsql/npgsql v4.0.14

https://github.com/npgsql/npgsql/releases/tag/v4.0.14
github_commit

commit f7e7ead0702d (npgsql/npgsql)

Fix landed in npgsql/npgsql commit f7e7ead0702d — awaiting tagged release

https://github.com/npgsql/npgsql/commit/f7e7ead0702d776a8f551f5786c4cac2d65c4bc6
github_commit Patch Available

commit e34e2ba8042e (npgsql/npgsql)

Patch available: npgsql/npgsql v4.0.16 (contains commit e34e2ba8042e)

https://github.com/npgsql/npgsql/commit/e34e2ba8042e666d9af54a1b255fba4d5b11df56
github_commit Patch Available

commit a22a42d8141d (npgsql/npgsql)

Patch available: npgsql/npgsql v7.0.7 (contains commit a22a42d8141d)

https://github.com/npgsql/npgsql/commit/a22a42d8141d7a3528f43c02c095a409507cf1af
github_commit Patch Available

commit 703d9af8fa48 (npgsql/npgsql)

Patch available: npgsql/npgsql v6.0.11 (contains commit 703d9af8fa48)

https://github.com/npgsql/npgsql/commit/703d9af8fa48dfe8c0180e36edb8278f34342d7b
github_commit Patch Available

commit 67acbe027e28 (npgsql/npgsql)

Patch available: npgsql/npgsql v4.1.13 (contains commit 67acbe027e28)

https://github.com/npgsql/npgsql/commit/67acbe027e28477ac2199e15cfb554bb2ffaf169
github_commit Patch Available

commit 3183efb2bdcc (npgsql/npgsql)

Patch available: npgsql/npgsql v5.0.18 (contains commit 3183efb2bdcc)

https://github.com/npgsql/npgsql/commit/3183efb2bdcca159c8c2e22af57e18ea8f853cf0
github_commit Patch Available

commit 091655eed0c8 (npgsql/npgsql)

Patch available: npgsql/npgsql v8.0.3 (contains commit 091655eed0c8)

https://github.com/npgsql/npgsql/commit/091655eed0c84e502ab424950c930339d17c1928

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
Npgsql7.0.0, 7.0.1, 7.0.2, 7.0.4, 7.0.67.0.7—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 191 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-32655?
CVE-2024-32655 is a high vulnerability published on May 14, 2024. Npgsql is the .NET data provider for PostgreSQL. The WriteBind() method in src/Npgsql/Internal/NpgsqlConnector.FrontendMessages.cs uses int variables to store the message length and the sum of parameter lengths. Both variables overflow when the sum of parameter lengths becomes too large. This…
When was CVE-2024-32655 disclosed?
CVE-2024-32655 was first published in the National Vulnerability Database on May 14, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-32655 actively exploited?
CVE-2024-32655 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 23.6% of all scored CVEs.
What is the CVSS score of CVE-2024-32655?
CVE-2024-32655 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2024-32655?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-32655, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-32655?

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

Start Free Scan →Browse All CVEs