EM-20261102-U5OE
VulnerabilityHigh severity
postgresql-odbc Vulnerability (CVE-2026-120065)
CVE-2026-120065
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 02 19:09 UTCC41 Red Hat Security Data
- Page Born
- Nov 02 19:18 UTCsecond source joined
- Last Signal
- Nov 02 19:18 UTC46 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 44 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 02 19:18 UTCC6 NVD published
- Scored: reachedNov 02 19:18 UTCCVSS 7.1 · EPSS 0.3%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 02 19:09 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-120065 (CVSS 7.1) (opens source in a new tab) For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC uses that column to identify rows. It places the column's name, as reported by the server, between double quotes in its k… High severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-120065 (important) (opens source in a new tab) postgresql-odbc: postgresql-odbc: SQL injection via unescaped column names in updatable cursors High severityVendorC41 Red Hat Security Data