CVE-2024-32655
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.72 % · percentile 77.80 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
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.
Read the publisher's advisoryNpgsql 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.
Read the publisher's advisoryNpgsql 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.
Read the publisher's advisory### Summary 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. ### Impact Attackers can issue arbitrary SQL statements to the database on behalf of the application. The final impact depends on the application that uses Npgsql, the data it stores in Postgres, etc.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.72 % · percentile 77.80 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2024-32655 · 15 Nov 2026 14:45:34 UTC
CVE-2024-32655 · 14 Nov 2026 16:37:01 UTC
CVE-2024-32655 · 13 Nov 2026 19:59:34 UTC
CVE-2024-32655 · 12 Nov 2026 18:18:51 UTC
CVE-2024-32655 · 10 Nov 2026 20:24:10 UTC
CVE-2024-32655 · 09 Nov 2026 21:04:24 UTC
CVE-2024-32655 · 08 Nov 2026 15:12:21 UTC
CVE-2024-32655 · 07 Nov 2026 16:07:52 UTC
CVE-2024-32655 · 06 Nov 2026 19:10:17 UTC
CVE-2024-32655 · 05 Nov 2026 22:49:22 UTC
CVE-2024-32655 · 05 Nov 2026 02:54:06 UTC
CVE-2024-32655 · 03 Nov 2026 16:59:18 UTC
CVE-2024-32655 · 02 Nov 2026 23:59:04 UTC
CVE-2024-32655 · 01 Nov 2026 23:58:58 UTC
CVE-2024-32655 · 01 Nov 2026 03:04:52 UTC
CVE-2024-32655 · 31 Oct 2026 01:52:30 UTC
CVE-2024-32655 · 29 Oct 2026 18:29:26 UTC
CVE-2024-32655 · 28 Oct 2026 19:55:37 UTC
CVE-2024-32655 · 27 Oct 2026 15:46:19 UTC
CVE-2024-32655 · 27 Oct 2026 00:23:05 UTC
CVE-2024-32655 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
euvd · EUVD-2024-1856 · Published
nvd · CVE-2024-32655 · Published
osv · GHSA-x9vc-6hfv-hg8c · Published
cve-program · CVE-2024-32655 · Published