CVE-2025-4953MediumMicrosoft CVSS 7.4CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U

Microsoft advisory for CVE-2025-4953 — azl3

Published
June 3, 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-2025-4953. This page also shows what EchelonGraph holds for CVE-2025-4953, 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 products3

  • azl3 conmon 2.1.8-1 on Azure Linux 3.0
  • azl3 runc 1.3.3-1 on Azure Linux 3.0
  • azl3 skopeo 1.14.4-6 on Azure Linux 3.0

🧭 EchelonGraph on CVE-2025-4953

EchelonGraph score
7.4 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 Podman. In a Containerfile or Podman, data written to RUN --mount=type=bind mounts during the podman build is not discarded. This issue can lead to files created within the container appearing in the temporary build context directory on the host, leaving the created files accessible.

Published by Red Hat, Inc., the CVE Numbering Authority that assigned CVE-2025-4953, 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 (1)