Microsoft security update for CVE-2026-77405 — azl3
🔗 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-77405. This page also shows what EchelonGraph holds for CVE-2026-77405, 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 products4
- azl3 keda 2.14.1-18 on Azure Linux 3.0
- azl3 keda 2.14.1-19 on Azure Linux 3.0
- azl3 telegraf 1.31.0-31 on Azure Linux 3.0
- azl3 telegraf 1.31.0-33 on Azure Linux 3.0
✅ Updates Microsoft lists: 3 updates
3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | — |
| — | Security Update | 2.14.1-21 |
| — | Security Update | 1.31.0-34 |
🧭 EchelonGraph on CVE-2026-77405
- EchelonGraph score
- 9.4 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
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, tlsConfigFromURI in uri.go creates tls.Config values without setting MinVersion to tls.VersionTLS12. Builds using a Go runtime whose default permits TLS 1.0 or TLS 1.1 can therefore negotiate an obsolete protocol version when connecting through an amqps URI. A network attacker able to influence TLS negotiation with such a legacy build may weaken transport protection for AMQP messages and credentials. This issue is fixed in version 1.13.0.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-77405, 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).