unixODBC: out-of-bounds memcpy

unixODBC

unixODBC versions <=2.3.14 vulnerable to out-of-bounds memcpy via narrowing conversion

Do this now

No source names a fix yet: limit who can reach unixODBC until one does.

First seen: 5 Nov 2026
Last update: 5 Nov 2026, 19:19 UTC
Source: news

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## unixODBC: out-of-bounds memcpy
Severity: unknown. Patch status: fix status unknown.
Affected: unixODBC

unixODBC versions <=2.3.14 vulnerable to out-of-bounds memcpy via narrowing conversion

## Steps
1. Search the repo, its CI and infra config for unixODBC. If present, report the version in use and whether it's affected.
2. No source names a fix yet; check the vendor advisory. Until one ships: restrict network access to it.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://seclists.org/oss-sec/2026/q4/520
https://pwned.coffee/i/unixodbc-out-of-bounds-memcpy

Timeline

5 Nov 2026, 19:19 UTC
Fix status: no fix yet → unknown.
5 Nov 2026
First reported.

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 6 Nov 2026, 12:18 UTC

Sources: KEV – CVE record – Vendor –

Sources

seclists.org: Fwd: 3 unixODBC<=2.3.14 issues from fulldisclosure mailing list

Follow on X

Totalone coffee