CVE-2026-109448
5.9MediumPublished 12 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Impact
- High impact on availability
- Weakness
- CWE-124, CWE-190
Impact
Attackers who control parameter counts in queries (like dynamic IN clauses) can corrupt application heap memory or crash the service. Exploitation requires sending queries configured with over 32,767 bound parameters.
Root cause
A signed 16-bit integer wraparound in SQLBindParameter causes an out-of-bounds write of zeros before the binding array when binding 32,768 or more parameters.
Affected systems
psqlODBC versions before 18.00.0005
CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Fix & remediation
Upgrade psqlODBC to version 18.00.0005 or later. As an interim workaround, enforce an application-level limit preventing queries from binding more than 32,767 parameters.
$ odbcinst -q -dAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.