Skip to main content
CVE-2026-116312VulnerabilityPublished

PostgreSQL MERGE · Inconsistent Transition-capture State

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116312· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium · fixed in 18.7 : update PostgreSQL when convenient.

Data as of 12 Nov 2026, 16:33 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PostgreSQL)CVSS 3.15.4
Patch
Available – fixed in 18.7, 17.12, 16.16 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade PostgreSQL and postgresql/postgresql to 18.7, 17.12, 16.16 or 15.20.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.7
Fixed in
  • 18.7
PostgreSQLAffected
  • >=17 <17.12
Fixed in
  • 17.12
PostgreSQLAffected
  • >=16 <16.16
Fixed in
  • 16.16
PostgreSQLAffected
  • >=15 <15.20
Fixed in
  • 15.20
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • >=15 <15.20
  • >=16 <16.16
  • >=17 <17.12
  • >=18 <18.7
Fixed in
  • 15.20
  • 16.16
  • 17.12
  • 18.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until patched, users should be cautious when using MERGE with partitioned tables and AFTER triggers. Monitoring vendor updates for fixed versions 15.20, 16.16, 17.12, and 18.7 is recommended.

Description

A vulnerability in PostgreSQL's MERGE command causes inconsistent transition-capture state, allowing an AFTER trigger to process an incorrect new row when using partitioned table MERGE operations that perform an INSERT before an UPDATE. This affects PostgreSQL major versions 15 through 18, specifically versions before 15.20, 16.16, 17.12, and 18.7. Versions prior to 15 are not affected.

References

Community reviews

Loading reviews…