CVE
PostgreSQL wrong row in MERGE trigger transition table
- Exploited
- No known exploitation
- Fix
- Fixed in 18.7, 17.12, 16.16, 15.20
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 18.7, 17.12, 16.16, 15.20.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.25% · 16th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
PostgreSQL's MERGE command can place the wrong row in a trigger transition table, which lets a user who can modify table data cause an AFTER trigger to process the wrong new row. The flaw is reached remotely over the network with low privileges and no user action, and it occurs when a MERGE on a partitioned table performs an INSERT before an UPDATE.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach17/20Affects PostgreSQL (a widely deployed server, runtime, framework or database)
- Severity5.4/10CVSS 5.4
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 44 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 18.7, 17.12, 16.16, 15.20.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-116312 (PostgreSQL MERGE can place the wrong row in a trigger transition table), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-116312 (entry last updated 2026-11-12):
Affected:
- n/a PostgreSQL: from 18, fixed in 18.7; from 17, fixed in 17.12; from 16, fixed in 16.16; from 15, fixed in 15.20
Fixed versions: 18.7, 17.12, 16.16, 15.20.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116312 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116312 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.postgresql.org/support/security/CVE-2026-116312/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-116312
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116312"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- n/a PostgreSQL
From 18 · fixed in 18.7; From 17 · fixed in 17.12; From 16 · fixed in 16.16; From 15 · fixed in 15.20
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116312
Is CVE-2026-116312 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-116312?
PostgreSQL: from 18 before 18.7; from 17 before 17.12; from 16 before 16.16; from 15 before 15.20.Source: cve.now feed data
How do I fix CVE-2026-116312?
Upgrade to a fixed version: 18.7, 17.12, 16.16, 15.20.Source: cve.now feed data