CVE-2025-61725MediumMicrosoft CVSS 6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2025-61725

Published
October 31, 2025
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-61725. This page also shows what EchelonGraph holds for CVE-2025-61725, 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 products15

  • azl3 golang 1.23.12-1 on Azure Linux 3.0
  • azl3 golang 1.25.10-1 on Azure Linux 3.0
  • azl3 golang 1.25.11-3 on Azure Linux 3.0
  • azl3 golang 1.25.12-1 on Azure Linux 3.0
  • azl3 golang 1.25.3-1 on Azure Linux 3.0
  • azl3 golang 1.25.5-1 on Azure Linux 3.0
  • azl3 golang 1.25.6-1 on Azure Linux 3.0
  • azl3 golang 1.25.7-1 on Azure Linux 3.0
  • 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.0-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.24.8-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-2025-61725

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

The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

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