Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4905-1 | postgresql-15 security update |
Wed, 18 Nov 2026 06:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 13 Nov 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql postgresql |
|
| Vendors & Products |
Postgresql
Postgresql postgresql |
Fri, 13 Nov 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-628 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 12 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PostgreSQL MERGE can place the wrong row in a trigger transition table | |
| Weaknesses | CWE-1250 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-11-17T17:14:43.345Z
Reserved: 2026-10-26T03:52:44.052Z
Link: CVE-2026-116312
Updated: 2026-11-17T17:12:05.259Z
Status : Awaiting Analysis
Published: 2026-11-12T15:17:39.190
Modified: 2026-11-17T18:17:47.653
Link: CVE-2026-116312
OpenCVE Enrichment
Updated: 2026-11-14T22:15:01Z
Debian DLA