
A package repository is part of a build system’s trust boundary. If a customer’s Azure Linux workflow uses libzypp, verify which repository data it processes and which privileges it holds.
What changed — November 19, 2026 UTC
CVE-2026-25707, CVE-2026-44941 and CVE-2026-44942: Microsoft’s June and July CVRF records now map Azure Linux 4.0 libzypp 17.38.1-5.azl4 to fixed build 0:17.38.13-6.azl4. Each record is revision 2.0 on November 19: 01:04:53, 01:08:08 and 01:08:13 UTC respectively. Their initial Microsoft revisions were published November 16. These are newly verified distribution fix mappings for older vulnerabilities, not newly disclosed attacks.
The exact fixed package is listed in checksum-verified official Microsoft build-dependency repository metadata for x86_64 and aarch64, and both RPM URLs loaded successfully. The binaries were hosted November 18. The reviewed base, cloud-native and Microsoft repository primary metadata did not list libzypp. This does not establish default host installation, inclusion in an Azure/AKS image or use by any customer.
Applicability, impact and severity
| CVE | Vendor-described path and upstream affected versions | Microsoft rating / CVSS v3.1 |
|---|---|---|
| CVE-2026-25707 | Attacker-supplied repository metadata can overwrite files, causing denial of service or privilege escalation. Upstream libzypp before 17.38.10. | Important / 8.8 |
| CVE-2026-44941 | Malicious repository keyhint data in repomd.xml can inject or overwrite files as root. Upstream before 17.38.12. | Important / 8.8 |
| CVE-2026-44942 | The path component in .repo files can place content outside the zypp cache and exhaust availability. Upstream 17.0.0 before 17.38.13, or versions before 16.22.19. | Moderate / 6.5 |
The Azure Linux affected/fixed matrix lists exact builds, not a verified lower bound for every older distribution package or backport. Upstream fixes are 17.38.10 for CVE-2026-25707, 17.38.12 for CVE-2026-44941 and 17.38.13 on the 17.x branch or 16.22.19 on the older branch for CVE-2026-44942. Use the supported distribution build rather than manually substituting an upstream version.
Score assessments differ. SUSE’s CNA scores are CVSS v3.1 8.8, 8.4 and 6.5 respectively. For CVE-2026-44941, its CNA vector requires high privileges and user interaction with changed scope, while Microsoft publishes 8.8 with no attacker privileges, user interaction and unchanged scope. SUSE’s separate product assessments are v3.1 7.4, 7.2 and 6.5; its pages also publish v4.0 7.5 for CVE-2026-44941 and 6.0 for CVE-2026-44942. Match the concrete repository-control and consumer-privilege prerequisites; do not interpret a network score as proof of a default internet-facing service.
Suggested MSP action
Suggested priority: High when affected libzypp processes untrusted or third-party repository data in a privileged build or provisioning workflow. Inventory the installed and loaded package, owning workflow, repository sources and execution privileges → pause untrusted repository inputs or restrict sources to approved repositories where needed → stage the supported Azure Linux 4.0 update to 0:17.38.13-6.azl4 → verify the actual consuming process uses the updated library and test representative repository refresh, package resolution and build/provisioning output. Rebuild separately maintained images that carry the affected library.
Source restriction is proposed exposure reduction, not a verified vendor workaround or replacement for patching. No vendor workaround was verified in the reviewed material. A package in a build-dependency repository is an applicability lead, not proof that customer workloads invoke it. No customer use, malicious repository, compromise or affected bundled appliance is assumed.
None of these three CVEs appears in the full current CISA KEV catalog; there is no associated federal KEV deadline. Confirmed active exploitation was not verified in the reviewed official material. No blanket vendor-directed compromise-check or credential-rotation requirement was identified. If suspicious repository activity is found, preserve evidence and investigate the consuming system separately from installing the update.
Official sources and review limits
Microsoft June CVRF · Microsoft July CVRF · SUSE CVE-2026-25707 · SUSE CVE-2026-44941 · SUSE CVE-2026-44942 · Microsoft x86_64 build-dependency metadata · Microsoft aarch64 build-dependency metadata · CISA official KEV data
Last verified November 19, 2026 ET. This entry covers the verified libzypp remediation cluster. Other pending Microsoft dependency records and existing vendor-source access gaps remain open.