CVE-2026-12080MediumMicrosoft CVSS 7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U

Microsoft security update for CVE-2026-12080 — azl3 qemu

Published
July 23, 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-12080. This page also shows what EchelonGraph holds for CVE-2026-12080, 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 qemu 10.1.0-1 on Azure Linux 3.0
  • azl3 qemu 10.1.0-2 on Azure Linux 3.0
  • azl3 qemu 9.1.0-10 on Azure Linux 3.0
  • azl3 qemu 9.1.0-11 on Azure Linux 3.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-12080

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

A flaw was found in the QEMU Guest Agent (qga). A local unprivileged user can exploit a vulnerability in the guest-ssh-add-authorized-keys command handler by manipulating symbolic links. This can occur either through a deterministic directory-symlink bypass or a Time-of-Check to Time-of-Use (TOCTOU) file-symlink race. Successful exploitation allows the attacker to gain ownership of arbitrary root-owned files or directories, leading to root access. This vulnerability requires an external management layer (e.g., libvirt) to trigger the affected code path.

Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2026-12080, 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)