# CVE-2026-109448: psqlODBC SQLBindParameter heap memory corruption when binding more than 32767 parameters

> An integer overflow in psqlODBC allows heap memory corruption and potential code execution when binding excessive parameters, affecting applications using the driver.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-109448, DEBIAN-CVE-2026-109448, GHSA-cmfx-rm3r-p2jr, UBUNTU-CVE-2026-109448, openSUSE-SU-2026:12135-1, openSUSE-SU-2026:22122-1

## What is CVE-2026-109448?

CVE-2026-109448 is a medium-severity vulnerability in PostgreSQL psqlODBC, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-124 (Buffer Underwrite)

## Which versions are affected by CVE-2026-109448?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `psqlODBC` | openSUSE:Leap 16.0 | All versions | 18.00.0005-bp160.1.1 |
| `psqlODBC` | openSUSE:Tumbleweed | All versions | 18.00.0005-1.1 |

## How do I fix CVE-2026-109448?

Upgrade to a fixed version.

## Is CVE-2026-109448 being exploited?

There is no known exploitation of CVE-2026-109448 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109448 and fix it if it is affected.

What it is: CVE-2026-109448 is a medium-severity vulnerability in PostgreSQL psqlODBC, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109448 in the wild and no public exploit code.

Affected product: PostgreSQL psqlODBC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109448/ (Markdown: https://insights.sbomify.com/CVE-2026-109448/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109448
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109448
- OSV: https://osv.dev/vulnerability/CVE-2026-109448

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109448/
Summaries are generated and may contain mistakes; the official description above is the record.