EM-20261112-541W
VulnerabilityHigh severity
PostgreSQL SQL-language Vulnerability (CVE-2026-18447)
CVE-2026-18447
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 12 14:15 UTCC41 Red Hat Security Data
- Page Born
- Nov 12 15:17 UTCsecond source joined
- Last Signal
- Nov 12 15:17 UTC24 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 10 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 ID never changes, and earlier addresses keep working. 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 12 15:17 UTCC6 NVD published
- Scored: reachedNov 12 15:17 UTCCVSS 8.8
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 12 14:15 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-18447 (CVSS 8.8) (opens source in a new tab) Type confusion in PostgreSQL SQL-language functions allows an object creator to execute arbitrary code as the operating system user running the database, via an output parameter of type "any". Versions before… High severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-18447 (important) (opens source in a new tab) postgresql: postgresql: Arbitrary code execution via type confusion in SQL-language functions High severityVendorC41 Red Hat Security Data