CVE-2026-3713MediumMicrosoft CVSS 5.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C

Microsoft security update for CVE-2026-3713

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-2026-3713. This page also shows what EchelonGraph holds for CVE-2026-3713, 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 products7

  • azl3 libpng 1.6.55-1 on Azure Linux 3.0
  • azl3 libpng 1.6.56-1 on Azure Linux 3.0
  • azl3 libpng 1.6.57-1 on Azure Linux 3.0
  • azl3 libpng 1.6.58-1 on Azure Linux 3.0
  • cbl2 libpng 1.6.55-1 on CBL Mariner 2.0
  • cbl2 libpng 1.6.56-1 on CBL Mariner 2.0
  • cbl2 libpng 1.6.56-1 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 1 update

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

KB articleUpdateFixed build
—Security Update—

🧭 EchelonGraph on CVE-2026-3713

EchelonGraph score
5.3 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

A flaw has been found in pnggroup libpng up to 1.6.55. Affected by this vulnerability is the function do_pnm2png of the file contrib/pngminus/pnm2png.c of the component pnm2png. This manipulation of the argument width/height causes heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Published by VulDB, the CVE Numbering Authority that assigned CVE-2026-3713, 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)