Event Monitor Cyber
EM-20261112-V6XV VulnerabilityHigh severity

PostgreSQL Vulnerability (CVE-2026-6460)

CVE-2026-6460

Share
Status
Developing

Since : signals keep joining.

First Signal
Nov 12 15:17 UTCC6 NVD CVE API 2.0
Page Born
Nov 12 16:21 UTCsecond source joined
Last Signal
Nov 12 16:21 UTC4 hours before snapshot
Sources
20 official · 2 research, news or crowd
Open For
1 hoursso far

Life Of This Page

  1. 1
    Born
    A second, independent source names it.
  2. 2
    Developing · Now
    New signals join; severity can move.
  3. 3
    Confirmed
    Not yet
    CISA KEV lists it, or exploitation in the wild is reported.
  4. 4
    Resolved
    Not yet
    Past the fix deadline and 14 days with no new signal.
  5. 5
    Archived
    Not yet
    30 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

  1. Disclosed: reached
    Nov 12 15:17 UTC
    C6 NVD published
  2. Scored: reached
    Nov 12 15:17 UTC
    CVSS 8.8
  3. Exploited: not yet
    Not yet
    No exploitation reported
  4. Advisories: not yet
    Not yet
    None yet
  5. Vendor Response: not yet
    Not yet
    None in sources yet
  6. Resolved: not yet
    Not yet
    After 14 quiet days

Timeline

10:0012:0014:0016:00BornC6 NVD CVE API 2.0C160 Reddit r/netsec

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

Signals

  1. prepared statements prevents SQLi. But it also helped me to exploit a 22 years old PostgreSQL 0-day RCE (CVE-2026-6460) (opens source in a new tab) submitted by /u/wtfse to r/netsec [link] [comments] Info severityCrowdC160 Reddit r/netsec
  2. CVE-2026-6460 (CVSS 8.8) (opens source in a new tab) Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ... SET DATA TYPE primarily. Other DDL attack routes exist, such as "ALTER… High severityDatabaseC6 NVD CVE API 2.0