CVE-2026-116306HighMicrosoft CVSS 8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Microsoft security update for CVE-2026-116306

Published
November 13, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-116306. This page also shows what EchelonGraph holds for CVE-2026-116306, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products4

  • azl3 postgresql 16.15-1 on Azure Linux 3.0
  • azl4 postgresql16 16.15-5.azl4 on Azure Linux 4.0
  • azl4 postgresql17 17.11-5.azl4 on Azure Linux 4.0
  • azl4 postgresql18 18.6-5.azl4 on Azure Linux 4.0

✅ Updates Microsoft lists: 4 updates

4 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update0:16.16-6.azl4
—Security Update0:17.12-6.azl4
—Security Update—
—Security Update16.16-1

🧭 EchelonGraph on CVE-2026-116306

EchelonGraph score
8.8 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

Type confusion in PostgreSQL composite-value field assignment allows an object creator to execute arbitrary code as the operating system user running the database, via changing a composite type between deforming and reforming a value. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Published by PostgreSQL, the CVE Numbering Authority that assigned CVE-2026-116306, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)