Postgresql · product
psqlODBC
12 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 12 is a mark on the map. Named now: 1 to 12, most at risk first.
- psqlODBC SQL injection through SQLSpecialColumns table and schema names
- psqlODBC stack buffer overflow copying ctid and oid values for updatable cursors
- psqlODBC does not validate column numbers and row indexes in binding and descriptor functions
- psqlODBC ODBC escape parser stack buffer overflow
- psqlODBC does not escape a server-supplied column name in its updatable-cursor queries
- psqlODBC stack buffer overflow when quoting long schema and table names
- psqlODBC uses a server-supplied column name as a format string
- psqlODBC row cache overflow when a later FETCH changes the column count
- psqlODBC large-object read overflows the application buffer
- psqlODBC SQLBindParameter heap memory corruption when binding more than 32767 parameters
- psqlODBC does not validate server-supplied counts and lengths
- psqlODBC log files are created with default permissions at a predictable path and follow symbolic links
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.