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

Microsoft security update for CVE-2026-39834

Published
May 28, 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-39834. This page also shows what EchelonGraph holds for CVE-2026-39834, 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 products14

  • azl3 cert-manager 1.12.15-6 on Azure Linux 3.0
  • azl3 cf-cli 8.7.11-5 on Azure Linux 3.0
  • azl3 docker-buildx 0.14.0-11 on Azure Linux 3.0
  • azl3 docker-compose 2.27.0-9 on Azure Linux 3.0
  • azl3 gh 2.62.0-15 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-23 on Azure Linux 3.0
  • azl3 kubernetes 1.30.10-25 on Azure Linux 3.0
  • azl3 kubevirt 1.7.1-2 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-17 on Azure Linux 3.0
  • azl3 moby-engine 25.0.3-18 on Azure Linux 3.0
  • azl3 nvidia-container-toolkit 1.17.8-2 on Azure Linux 3.0
  • azl3 packer 1.9.5-13 on Azure Linux 3.0
  • azl3 telegraf 1.31.0-19 on Azure Linux 3.0
  • azl4 gvisor-tap-vsock 6:0.8.9-2.azl4 on Azure Linux 4.0

✅ Updates Microsoft lists: 12 updates

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

KB articleUpdateFixed build
—Security Update1.12.15-8
—Security Update8.7.11-6
—Security Update0.14.0-13
—Security Update2.27.0-11
—Security Update2.62.0-16
—Security Update1.30.10-25
—Security Update1.7.1-5
—Security Update25.0.3-18
—Security Update1.17.8-3
—Security Update1.9.5-14
—Security Update1.31.0-21
—Security Update6:0.9.0-2.azl4

🧭 EchelonGraph on CVE-2026-39834

EchelonGraph score
9.1 CRITICAL
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

When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.

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