Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade to psqlODBC 18.00.0005 or later. SQLBindParameter now rejects parameter numbers outside 1..32767 with SQLSTATE 07009 (invalid descriptor index).
Vendor Workaround
Do not bind more than 32767 parameters on a single statement. Limit the number of parameters an application builds from external input, or pass large value lists as a single array parameter, for example = ANY(?).
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 12 Oct 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql psqlodbc |
|
| Vendors & Products |
Postgresql
Postgresql psqlodbc |
Mon, 12 Oct 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Integer wraparound in psqlODBC SQLBindParameter allows an application, or an attacker who controls how many parameters the application binds on one statement, to corrupt heap memory. psqlODBC stores the binding count in a signed 16-bit field. Binding parameter number 32768 wraps that count to -32768. Binding parameter 32769 then writes about 2.5 MB of zeros starting 1.25 MB before the binding array, which crashes the application or leaves it running on a corrupted heap. Applications that build parameter lists from untrusted input, such as an IN (?, ?, ...) list, are exposed. Versions before psqlODBC 18.00.0005 are affected. | |
| Title | psqlODBC SQLBindParameter heap memory corruption when binding more than 32767 parameters | |
| Weaknesses | CWE-124 CWE-190 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-10-12T17:42:59.581Z
Reserved: 2026-10-12T16:34:39.636Z
Link: CVE-2026-109448
No data.
Status : Received
Published: 2026-10-12T18:17:22.633
Modified: 2026-10-12T18:17:22.633
Link: CVE-2026-109448
No data.
OpenCVE Enrichment
Updated: 2026-10-12T20:30:14Z