CVE-2026-116312: PostgreSQL MERGE can place the wrong row in a trigger transition table
Vendor not named in the CVE record · PostgreSQL
Vendor fix available · Affected: PostgreSQL · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 16% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- PostgreSQLfrom 18 before 18.7; from 17 before 17.12; from 16 before 16.16; from 15 before 15.20
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-116312 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.