CVE-2026-78662MediumMicrosoft CVSS 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U

Microsoft security update for CVE-2026-78662 — azl3

Published
September 11, 2026
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2026-78662 →

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

  • azl3 cert-manager 1.12.15-11 on Azure Linux 3.0
  • azl3 cert-manager 1.12.15-12 on Azure Linux 3.0
  • azl3 cf-cli 8.7.11-8 on Azure Linux 3.0
  • azl3 cf-cli 8.7.11-9 on Azure Linux 3.0
  • azl3 docker-buildx 0.14.0-16 on Azure Linux 3.0
  • azl3 docker-buildx 0.14.0-17 on Azure Linux 3.0
  • azl3 docker-compose 2.27.0-13 on Azure Linux 3.0
  • azl3 docker-compose 2.27.0-14 on Azure Linux 3.0
  • azl3 gh 2.62.0-20 on Azure Linux 3.0
  • azl3 gh 2.98.0-1 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-27 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-29 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-30 on Azure Linux 3.0
  • azl3 kubevirt 1.7.1-8 on Azure Linux 3.0
  • azl3 kubevirt 1.8.4-1 on Azure Linux 3.0
  • azl3 kubevirt 1.8.4-2 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-19 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-20 on Azure Linux 3.0
  • azl3 packer 1.9.5-18 on Azure Linux 3.0
  • azl3 packer 1.9.5-20 on Azure Linux 3.0
  • azl3 packer 1.9.5-21 on Azure Linux 3.0
  • azl3 telegraf 1.31.0-28 on Azure Linux 3.0
  • azl3 telegraf 1.31.0-31 on Azure Linux 3.0

✅ Updates Microsoft lists: 17 updates

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

KB articleUpdateFixed build
—Security Update—
—Security Update1.12.15-14
—Security Update2.27.0-14
—Security Update8.7.11-9
—Security Update0.14.0-17
—Security Update2.27.0-14
—Security Update2.101.0-1
—Security Update1.30.10-30
—Security Update1.8.4-2
—Security Update25.0.3-21
—Security Update1.9.5-21
—Security Update1.31.0-33
—Security Update8.7.11-9
—Security Update0.14.0-17
—Security Update1.30.10-30
—Security Update1.8.4-2
—Security Update1.9.5-21

🧭 EchelonGraph on CVE-2026-78662

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

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.

Published by Go Project, the CVE Numbering Authority that assigned CVE-2026-78662, 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)