CVE-2026-32289MediumMicrosoft CVSS 6.1CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N/E:U

Microsoft security update for CVE-2026-32289

Published
June 2, 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-32289. This page also shows what EchelonGraph holds for CVE-2026-32289, 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 golang 1.25.8-1 on Azure Linux 3.0
  • azl3 golang 1.25.9-1 on Azure Linux 3.0
  • azl3 golang 1.26.1-1 on Azure Linux 3.0
  • azl3 golang 1.26.2-1 on Azure Linux 3.0
  • azl3 golang 1.27.0-1 on Azure Linux 3.0
  • cbl2 golang 1.18.8-10 on CBL Mariner 2.0
  • cbl2 golang 1.22.7-5 on CBL Mariner 2.0
  • cbl2 msft-golang 1.25.8-1 on CBL Mariner 2.0
  • cbl2 msft-golang 1.25.8-1 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 2 updates

2 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 Update—

🧭 EchelonGraph on CVE-2026-32289

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

Context was not properly tracked across template branches for JS template literals, leading to possibly incorrect escaping of content when branches were used. Additionally template actions within JS template literals did not properly track the brace depth, leading to incorrect escaping being applied. These issues could cause actions within JS template literals to be incorrectly or improperly escaped, leading to XSS vulnerabilities.

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