CVE-2025-4207MediumMicrosoft CVSS 5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2025-4207

Published
May 31, 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-2025-4207. This page also shows what EchelonGraph holds for CVE-2025-4207, 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 products9

  • azl3 postgresql 16.7-1 on Azure Linux 3.0
  • azl3 postgresql 16.9-1 on Azure Linux 3.0
  • azl3 rust 1.75.0-22 on Azure Linux 3.0
  • azl3 rust 1.90.0-1 on Azure Linux 3.0
  • azl3 rust 1.90.0-3 on Azure Linux 3.0
  • azl3 rust 1.90.0-4 on Azure Linux 3.0
  • cbl2 postgresql 14.16-1 on CBL Mariner 2.0
  • cbl2 postgresql 14.16-1 on CBL-Mariner 2.0
  • cm2 postgresql 14.18-1 on CBL Mariner 2.0

✅ Updates Microsoft lists: 3 updates

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

KB articleUpdateFixed build
—Security Update14.18-1
—Security Update16.9-1
—Security Update1.90.0-4

🧭 EchelonGraph on CVE-2025-4207

EchelonGraph score
5.9 MEDIUM
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

Buffer over-read in PostgreSQL GB18030 encoding validation allows a database input provider to achieve temporary denial of service on platforms where a 1-byte over-read can elicit process termination. This affects the database server and also libpq. Versions before PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21 are affected.

Published by PostgreSQL, the CVE Numbering Authority that assigned CVE-2025-4207, 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)