Azure Linux Rust fix is available for build runners

If your Azure Linux build runners fetch source or dependencies over SSH, check which Rust RPM the jobs actually use. Microsoft’s patched package is now available in production for x64 and Arm64.

Amber fiber cable curving toward a black server in a rack.

What changed November 14, 2026 UTC. Microsoft’s Azure Linux 3.0 production repositories now list rust 1.98.1-2.azl3 for both architectures. Microsoft merged the six backports November 7. The original vulnerability disclosures span June 17 to October 12, 2026. Last verified November 14, 2026 UTC.

Which builds and workflows are affected

Vendored libssh2. CVE-2026-55200 can allow code execution in a client connecting to a malicious SSH server. The assigning CNA rates it Critical, CVSS 9.2 v4.0 and 8.1 v3.1. CVE-2026-55199 can exhaust client CPU before authentication. CVE-2026-66035 is a pre-authentication heap overflow during Encrypt-then-MAC negotiation. Microsoft’s standalone libssh2 rows score those two 5.9 and 7.5 respectively, both CVSS v3.1. Microsoft’s Azure Linux vulnerability data lists rust from 1.85.0 through 1.98.1-1 for these three issues.

Vendored Gitoxide. CVE-2026-109349 and CVE-2026-109351 can interrupt clone or fetch operations from a malicious Git remote. CVE-2026-91986 affects Git transport input handling. Microsoft rates these Moderate 6.5, Important 6.5, and Low 5.4 respectively, all CVSS v3.1. The shared affected row is rust 1.98.1-1. Microsoft also lists 1.75.0-31 for all three, 1.96.1-2 for CVE-2026-109349 and CVE-2026-91986, and 1.96.1-1 for CVE-2026-91986. Microsoft’s backport notes say the transport patch still allows carriage return and the allocation fix has no explicit size cap.

Exploitation. The Microsoft records reviewed give no exploitation assessment for these package issues. CISA KEV lists none of the six. Affected packages alone do not establish that a runner exercises the vulnerable client path.

Rollout and verification

Suggested MSP priority. Prioritize shared or credentialed runners that fetch from user-controlled or otherwise untrusted SSH or Git remotes. Inventory the RPM and the actual build images, pinned runners, and vendored clients. Restrict fetches to approved remotes and keep untrusted jobs off credentialed runners while rolling out the fix. Those controls reduce exposure while the underlying package remains vulnerable.

Update to Microsoft’s rust 1.98.1-2.azl3 on the verified production channel. Rebuild and redeploy pinned or containerized runner images that use that RPM. Verify the installed RPM release inside the running job and test a trusted fetch. Check separately distributed Cargo, libssh2, and custom vendored builds against their own package or image sources. Managed AKS image delivery and independently distributed packages were outside this RPM verification. The reviewed Microsoft sources provide no incident-specific rotation or compromise-check requirement for this update.

Official sources. Microsoft x64 RPM index, Microsoft Arm64 RPM index, Microsoft backport and limitations, Microsoft AZL-108519, Microsoft AZL-108513, Microsoft AZL-108528, MSRC Jun CVRF, MSRC Jul CVRF, MSRC Sep CVRF, MSRC Oct CVRF, CVE-2026-55200 CNA record, Microsoft Azure Linux update and verification guidance, CISA KEV data.

Share this article