Threat Overview
On November 12, the PostgreSQL Global Development Group released 18.7, 17.12, 16.16, 15.20 and 14.25, correcting 52 vulnerabilities. CVE-2026-6460 is a type-confusion flaw that can let an authenticated database object creator execute code with the PostgreSQL service account’s operating-system privileges. Related code-execution fixes include CVE-2026-120139 and CVE-2026-120150. This is not unauthenticated remote execution; database access and appropriate object privileges matter.
References
https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/ (published November 11–13, 2026; see source)
https://www.postgresql.org/support/security/CVE-2026-6460/ (published November 11–13, 2026; see source)
Impacted Systems
PostgreSQL core server 14–18 before 14.25, 15.20, 16.16, 17.12, 18.7 respectively. Self-managed Linux and Windows database servers; managed-service patching must be confirmed separately. PostgreSQL 14 is end-of-life following 14.25.
Why this matters
Authenticated application/database account compromise can turn into database service-account execution and follow-on host intrusion. Prioritize systems exposing PostgreSQL to broad networks or granting unneeded CREATE rights.
Exploitation Status
Vendor confirmed vulnerability and fixes November 12; no confirmed in-the-wild exploitation was reported. These hunts target suspicious post-exploitation behavior and cannot prove a particular CVE.
What this hunt looks for
Behavioral endpoint, identity and network activity consistent with the described threat; no customer-specific results are claimed.
Required logs
DeviceProcessEvents, DeviceNetworkEvents, DeviceFileEvents, SecurityEvent, Syslog; PostgreSQL audit logs require separate ingestion and parsing.
P01 — PostgreSQL spawning shells
DeviceProcessEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ('postgres.exe','postgres','postmaster')
| where FileName in~ ('cmd.exe','powershell.exe','pwsh.exe','bash','sh','python','python3','curl','wget')
| project TimeGenerated,DeviceName,AccountName,FileName,ProcessCommandLineP02 — PostgreSQL public outbound connections
DeviceNetworkEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ('postgres.exe','postgres','postmaster')
| where isnotempty(RemoteIP) and ipv4_is_private(RemoteIP) == false
| summarize Hits=count() by DeviceName,RemoteIP,RemotePortP03 — Script creation by PostgreSQL
DeviceFileEvents
| where TimeGenerated >= ago(30d)
| where InitiatingProcessFileName in~ ('postgres.exe','postgres','postmaster')
| where FileName endswith '.ps1' or FileName endswith '.sh' or FileName endswith '.exe' or FileName endswith '.dll'
| project TimeGenerated,DeviceName,FolderPath,FileName,ActionTypeP04 — Database errors and DDL in Linux Syslog
Syslog
| where TimeGenerated >= ago(30d)
| where ProcessName has_any ('postgres','postmaster') or SyslogMessage has 'postgres'
| where SyslogMessage has_any ('ALTER TABLE','SET DATA TYPE','segmentation fault','core dumped','CREATE EXTENSION')
| project TimeGenerated,Computer,ProcessName,SyslogMessageP05 — Windows database-related process events
SecurityEvent
| where TimeGenerated >= ago(30d) and EventID == 4688
| where CommandLine has_any ('postgres.exe','psql.exe','pg_restore.exe','pg_dump.exe') or ParentProcessName has 'postgres'
| project TimeGenerated,Computer,Account,NewProcessName,ParentProcessName,CommandLineP06 — New PostgreSQL network destinations
let baseline = DeviceNetworkEvents | where TimeGenerated between (ago(30d)..ago(2d)) | where InitiatingProcessFileName in~ ('postgres.exe','postgres','postmaster') | distinct DeviceName,RemoteIP;
DeviceNetworkEvents
| where TimeGenerated >= ago(2d)
| where InitiatingProcessFileName in~ ('postgres.exe','postgres','postmaster') and isnotempty(RemoteIP)
| join kind=leftanti baseline on DeviceName,RemoteIP
| summarize FirstSeen=min(TimeGenerated),Hits=count() by DeviceName,RemoteIP,RemotePortDetection Notes
Most useful signals are PostgreSQL spawning shell tools, writing scripts, or making new public outbound connections. Legitimate migrations and backup jobs can generate noise. No query uniquely identifies exploitation of CVE-2026-6460.
Queries have not been executed in customer Sentinel workspaces. Findings depend on ingested sources and retention; absence of matching telemetry does not establish absence of compromise.