Skip to content
VulniPulse
High7.4Vendor: MediumRed Hat Linux

High [CVE-2025-4953] Podman: build context bind mount

This high-severity Red Hat Linux advisory covers CVE-2025-4953 affecting Red Hat Enterprise Linux 8, Red Hat OpenShift Container Platform 4.12, Red Hat OpenShift Container Platform 4.13.

CVE-2025-4953 Published Sep 16, 2025Updated by vendor Sep 16, 2025
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

This issue is classified as Moderate rather than Important because exploitation requires several preconditions: an attacker must have unprivileged access to the host during the build process, the container build must include long-running steps (e.g., RUN sleep) that prolong the existence of the temporary build context, and files must be created with overly permissive permissions (e.g., 4777).

The vulnerability does not allow remote code execution or compromise of running containers, and it only exposes files temporarily present in the build context. Therefore, while it can lead to information disclosure, the scope and impact are limited to local users with concurrent access, making the overall risk moderate.

Red Hat severity: Moderate — CVSS 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). Weakness: CWE-378.

Affected products named by the advisory: Red Hat Enterprise Linux 8; Red Hat OpenShift Container Platform 4.12; Red Hat OpenShift Container Platform 4.13; Red Hat OpenShift Container Platform 4.14; and 4 more.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • container-tools:rhel8-8100020250911075811.afee755d
  • podman-3:4.2.0-15.rhaos4.12.el9
  • rhcos-412.86.202601061735-0
  • buildah-1:1.29.1-5.rhaos4.13.el9
  • conmon-3:2.1.7-5.rhaos4.13.el8
  • containernetworking-plugins-1:1.4.0-5.rhaos4.13.el8
  • cri-o-0:1.26.5-26.rhaos4.13.giteb3d487.el8
  • cri-tools-0:1.26.0-7.el8
  • haproxy-0:2.2.24-5.rhaos4.13.el8
  • ignition-0:2.15.0-10.rhaos4.13.el9
  • openshift-0:4.13.0-202410181847.p0.g53fd427.assembly.stream.el8
  • openshift4-aws-iso-0:4.13.0-202410181847.p0.gd2acdd5.assembly.stream.el8
  • openshift-ansible-0:4.13.0-202410181847.p0.g1397e80.assembly.stream.el8
  • openshift-clients-0:4.13.0-202410181847.p0.gd192e90.assembly.stream.el8
  • openshift-kuryr-0:4.13.0-202410181847.p0.g36754b7.assembly.stream.el8
  • podman-3:4.4.1-15.rhaos4.13.el8
  • runc-4:1.1.14-2.rhaos4.13.el8
  • skopeo-2:1.11.3-4.rhaos4.13.el8
  • buildah-1:1.29.5-1.rhaos4.13.el8
  • kernel-0:5.14.0-284.109.1.el9_2
  • kernel-rt-0:5.14.0-284.109.1.rt14.394.el9_2
  • podman-3:4.4.1-16.rhaos4.13.el8
  • rhcos-413.92.202511261311-0
  • rhcos-414.92.202512031525-0
  • rhcos-415.92.202512100122-0
  • podman-4:4.9.4-16.rhaos4.16.el8
  • rhcos-416.94.202512030118-0
  • rhcos-417.94.202511260612-0
  • podman-5:5.2.2-2.rhaos4.18.el8
  • rhcos-418.94.202512022246-0
  • RHSA-2025:15904
  • RHSA-2025:17669
  • RHSA-2026:0316
  • RHSA-2024:8690
  • RHSA-2025:2703
  • RHSA-2025:22275
  • RHSA-2025:22732
  • RHSA-2025:23113
  • RHSA-2025:16724
  • RHSA-2025:22724
  • RHSA-2025:22265
  • RHSA-2025:16729
  • RHSA-2025:22695

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.