nday
CVE-2026-116312

PostgreSQL MERGE can place the wrong row in a trigger transition table

Technical analysis appeared on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

network
AV:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (CVSS 3.1) from the CNA PostgreSQL
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (CVSS 3.1) from the CNA PostgreSQL
stage
ANA
disclosed
cvss
5.4 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
11-12T14:15Z
PATpatch
no record yet
ANAanalysis
11-12T17:59Z
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

Inconsistent transition-capture state in PostgreSQL MERGE allows a table data modifier to make an AFTER trigger process the wrong new row, via a partitioned table MERGE that performs an INSERT before an UPDATE. Within major versions 15-18, minor versions before PostgreSQL 18.7, 17.12, 16.16, and 15.20 are affected. Versions before PostgreSQL 15 are unaffected.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CVSS 3.1 vector from the CVE record, scored by the CNA PostgreSQL.

Event log

+DISdisclosed

CVE record published by PostgreSQL. CVSS 5.4, medium.

src cvelist · nday , observed live · raw
{
  "id": 17763,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-116312",
  "occurred_at": "2026-11-12T14:15:06.946Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
      "version": "3.1",
      "base_score": 5.4,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2026-11-17T17:07:58.003871Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-12T14:15:06.946Z",
    "assigner_short_name": "PostgreSQL"
  }
}
+ANAtechnical analysis

Posted to the oss-security mailing list: “PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released, fixes 52 security vulnerabilities”.

src osssec 2026/q4/682 · nday , observed live · raw
{
  "id": 496515,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/682",
  "occurred_at": "2026-11-12T17:59:21Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/682",
  "detail": {
    "list": "oss-security",
    "author": "Alan Coopersmith",
    "subject": "PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25, and 19 RC 2 Released, fixes 52 security vulnerabilities",
    "is_reply": false
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.