CVE-2026-6460

validatedZero produced an exploit or a check.

GHSA-7m3p-q8w8-4qgh ↗EUVD-2026-124433 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+17h25mkevAttacks confirmed in the real world.
PostgreSQL >= 18, < 18.7; >= 17, < 17.12; >= 16, < 16.16; >= 15, < 15.20; < 14.25
fixed in 18.7, 17.12, 16.16, 15.20, 14.25
ETK-2026-4678Zero's internal tracking ID, independent of the CVE number., permanent identifier
+5.1dTTV
27mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dpublic poc+0.7dcheck available+5.1dagent stopped
0
+1d
+2d
+3d
+4d

description

PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, and 14.25 are affected by a type-confusion flaw in DDL processing. An authenticated user with permissions to create or modify database objects may be able to execute code as the operating-system account that runs the database.

mitigation

Upgrade PostgreSQL to 18.7, 17.12, 16.16, 15.20, or 14.25, as appropriate for the supported major version. Until upgraded, restrict untrusted users from creating or modifying database objects.

fixed in 18.7, 17.12, 16.16, 15.20, 14.25

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.59%48th percentile
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 14:15Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+17h25m
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-12 14:15Z
  2. 2026-11-12 14:15Z
  3. 2026-11-17 13:26Z
    PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
  4. 2026-11-17 14:55Z

this entry in the feed

GET /api/v1/feed/CVE-2026-6460

{
  "etk_id": "ETK-2026-4678",
  "cve_id": "CVE-2026-6460",
  "display_id": "CVE-2026-6460",
  "ghsa_id": "GHSA-7m3p-q8w8-4qgh",
  "euvd_id": "EUVD-2026-124433",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Type confusion in PostgreSQL DDL handling",
  "summary": "PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, and 14.25 are affected by a type-confusion flaw in DDL processing. An authenticated user with permissions to create or modify database objects may be able to execute code as the operating-system account that runs the database.",
  "mitigation": "Upgrade PostgreSQL to 18.7, 17.12, 16.16, 15.20, or 14.25, as appropriate for the supported major version. Until upgraded, restrict untrusted users from creating or modifying database objects.",
  "vendor": null,
  "product": "PostgreSQL",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 18, < 18.7",
        ">= 17, < 17.12",
        ">= 16, < 16.16",
        ">= 15, < 15.20",
        ">= 0, < 14.25"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "18.7",
        "17.12",
        "16.16",
        "15.20",
        "14.25"
      ],
      "package_name": "PostgreSQL",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0059,
  "epss_percentile": 0.4884,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 26.77341225,
  "t0_at": "2026-11-12T14:15:32.415000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-17T16:51:04.116531+00:00",
      "days": 5.108005804756944,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T14:15:32.415000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-11-13T07:40:19+00:00",
      "days": 0.7255391782407408,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T14:15:32.415000+00:00",
      "url": "https://github.com/slabbdev/postgresql-type-confusion-cve-2026-6460"
    },
    "trigger_signal": {
      "at": "2026-11-12T14:15:32.415000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T14:15:32.415000+00:00",
      "url": "https://thehackernews.com/2026/11/postgresql-patches-52-flaws-including.html"
    }
  }
}

published 2026-11-17 14:50Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.