Skip to content
Fencer Intel
high 7.4

CVE-2025-4953 json

Podman: build context bind mount

published last yr. modified 4d ago also EUVD-2025-29612 , GHSA-m68q-4hqr-mc6f , GO-2025-3961

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

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.

Patch / fix

  • Red Hat Red Hat Enterprise Linux 8 8100020250911075811.afee755d
  • Red Hat Red Hat OpenShift Container Platform 4.12 3:4.2.0-15.rhaos4.12.el9, 412.86.202601061735-0
  • Red Hat Red Hat OpenShift Container Platform 4.13 0:1.26.0-7.el8, 0:1.26.5-26.rhaos4.13.giteb3d487.el8, 0:2.2.24-5.rhaos4.13.el8, 0:2.15.0-10.rhaos4.13.el9, 0:4.13.0-202410181847.p0.g53fd427.assembly.stream.el8, 0:4.13.0-202410181847.p0.g1397e80.assembly.stream.el8, 0:4.13.0-202410181847.p0.g36754b7.assembly.stream.el8, 0:4.13.0-202410181847.p0.gd2acdd5.assembly.stream.el8, 0:4.13.0-202410181847.p0.gd192e90.assembly.stream.el8, 0:5.14.0-284.109.1.el9_2, 0:5.14.0-284.109.1.rt14.394.el9_2, 1:1.4.0-5.rhaos4.13.el8, 1:1.29.1-5.rhaos4.13.el9, 1:1.29.5-1.rhaos4.13.el8, 2:1.11.3-4.rhaos4.13.el8, 3:2.1.7-5.rhaos4.13.el8, 3:4.4.1-15.rhaos4.13.el8, 3:4.4.1-16.rhaos4.13.el8, 4:1.1.14-2.rhaos4.13.el8, 413.92.202511261311-0
  • Red Hat Red Hat OpenShift Container Platform 4.14 414.92.202512031525-0
  • Red Hat Red Hat OpenShift Container Platform 4.15 415.92.202512100122-0
  • Red Hat Red Hat OpenShift Container Platform 4.16 4:4.9.4-16.rhaos4.16.el8, 416.94.202512030118-0
  • Red Hat Red Hat OpenShift Container Platform 4.17 417.94.202511260612-0
  • Red Hat Red Hat OpenShift Container Platform 4.18 5:5.2.2-2.rhaos4.18.el8, 418.94.202512022246-0
  • podman Debian 14, Debian 13 5.3.2+ds1-1

debian advisories DEBIAN-CVE-2025-4953

  • perf openshift 4.12 4.18.0-372.164.1.el8_6
  • kernel openshift 4.12 4.18.0-372.164.1.el8_6
  • podman openshift 4.12 3:4.4.1-10.rhaos4.12.el8
  • podman openshift 4.12 3:4.2.0-15.rhaos4.12.el9
  • bpftool openshift 4.12 4.18.0-372.164.1.el8_6
  • kernel-rt openshift 4.12 4.18.0-372.164.1.rt7.325.el8_6
  • kernel-core openshift 4.12 4.18.0-372.164.1.el8_6
  • kernel-tools openshift 4.12 4.18.0-372.164.1.el8_6

red hat advisories RHSA-2025:17669RHSA-2025:16729RHSA-2025:16724RHSA-2025:15904RHSA-2025:2703RHSA-2024:8690

  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20250918T182144-150000.1.107.1

suse advisories SUSE-SU-2025:03289-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250917T170349-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15564-1

  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1872+2e18eb19
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1815+5fe7415e
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1896+b18fa106
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1880+8e896d1b
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1825+623b0c20
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+2001+6a33db9f
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1874+ce489889
  • criu Rocky Linux 8 3.18-5.module+el8.10.0+1843+6892ab28

rocky linux advisories RLSA-2025:15904

  • podman Azure Linux 3.0 5.6.1-2

azure linux advisories AZL-68054

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2025-4953 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-4953 updated cvss 7.4

podman: Build Context Bind Mount

  • Red Hat Enterprise Linux AppStream (v. 8) crit 3.18-5.module+el8.10.0+23498+f7d19d48, criu 3.18-5.module+el8.10.0+23498+f7d19d48, crun 1.14.3-2.module+el8.10.0+23498+f7d19d48, runc 1.1.12-6.module+el8.10.0+23498+f7d19d48, udica 0.2.6-21.module+el8.10.0+23498+f7d19d48, conmon 2.1.10-1.module+el8.10.0+23498+f7d19d48, +27 more
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:15904
  • Red Hat OpenShift Container Platform 4.12 rhcos 412.86.202601061735, podman 4.2.0-15.rhaos4.12.el9, podman 4.4.1-10.rhaos4.12.el8, podman-tests 4.2.0-15.rhaos4.12.el9, podman-tests 4.4.1-10.rhaos4.12.el8, podman-docker 4.2.0-15.rhaos4.12.el9, +9 more
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:17669
  • Red Hat OpenShift Container Platform 4.13 cri-tools 1.26.0-7.el8, cri-tools 1.26.0-7.el9, rhcos 413.92.202511261311, perf 5.14.0-284.109.1.el9_2, rtla 5.14.0-284.109.1.el9_2, runc 1.1.14-2.rhaos4.13.el8, +134 more
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:2703
  • Red Hat OpenShift Container Platform 4.14 rhcos 414.92.202512031525
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:22732
  • Red Hat OpenShift Container Platform 4.15 rhcos 415.92.202512100122
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:23113
  • Red Hat OpenShift Container Platform 4.16 rhcos 416.94.202512030118, podman 4.9.4-16.rhaos4.16.el8, podman 4.9.4-18.rhaos4.16.el9, podman-tests 4.9.4-16.rhaos4.16.el8, podman-tests 4.9.4-18.rhaos4.16.el9, podman-docker 4.9.4-16.rhaos4.16.el8, +7 more
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:16724
  • Red Hat OpenShift Container Platform 4.17 rhcos 417.94.202511260612
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:22265
  • Red Hat OpenShift Container Platform 4.18 rhcos 418.94.202512022246, podman 5.2.2-2.rhaos4.18.el8, podman-tests 5.2.2-2.rhaos4.18.el8, podman-docker 5.2.2-2.rhaos4.18.el8, podman-remote 5.2.2-2.rhaos4.18.el8, podman-gvproxy 5.2.2-2.rhaos4.18.el8, +2 more
    fixed: vendor fix “Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.” RHSA-2025:16729
show 2 more
  • Red Hat Enterprise Linux 9 podman, podman-tests, podman-docker, podman-remote, podman-gvproxy, podman-plugins, +1 more
    not affected: inline mitigations already exist
  • Red Hat Enterprise Linux 10 podman Red Hat OpenShift Container Platform 4.12 perf 4.18.0-372.164.1.el8_6, kernel 4.18.0-372.164.1.el8_6, bpftool 4.18.0-372.164.1.el8_6, kernel-core 4.18.0-372.164.1.el8_6, kernel-tools 4.18.0-372.164.1.el8_6, python3-perf 4.18.0-372.164.1.el8_6, +32 more Red Hat OpenShift Container Platform 4.16 container-selinux 2.237.0-2.rhaos4.16.el9, openshift 4.16.0-202509111927.p2.gf3d9123.assembly.stream.el8, openshift 4.16.0-202509111927.p2.gf3d9123.assembly.stream.el9, openshift-kubelet 4.16.0-202509111927.p2.gf3d9123.assembly.stream.el8, openshift-kubelet 4.16.0-202509111927.p2.gf3d9123.assembly.stream.el9, openshift-hyperkube 4.16.0-202509111927.p2.gf3d9123.assembly.stream.el8, +7 more Red Hat OpenShift Container Platform 4.18 openshift 4.18.0-202509240609.p2.ge2e5d62.assembly.stream.el8, openshift 4.18.0-202509240609.p2.ge2e5d62.assembly.stream.el9, openshift-kubelet 4.18.0-202509240609.p2.ge2e5d62.assembly.stream.el8, openshift-kubelet 4.18.0-202509240609.p2.ge2e5d62.assembly.stream.el9, openshift-hyperkube 4.18.0-202509240609.p2.ge2e5d62.assembly.stream.el8, openshift-hyperkube 4.18.0-202509240609.p2.ge2e5d62.assembly.stream.el9, +6 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/containers/podman/v5
<=5.5.0
all versions
 no fix listed
go github.com/containers/podman
all versions
 no fix listed
go github.com/containers/podman/v2
all versions
 no fix listed
go github.com/containers/podman/v3
all versions
 no fix listed
go github.com/containers/podman/v4
all versions
 no fix listed

Affected products

  • containers podman
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat OpenShift Container Platform 4.12
  • Red Hat Red Hat OpenShift Container Platform 4.13
  • Red Hat Red Hat OpenShift Container Platform 4.14
  • Red Hat Red Hat OpenShift Container Platform 4.15
  • Red Hat Red Hat OpenShift Container Platform 4.16
  • Red Hat Red Hat OpenShift Container Platform 4.17
  • Red Hat Red Hat OpenShift Container Platform 4.18
  • Red Hat Red Hat Enterprise Linux 10
  • Red Hat Red Hat Enterprise Linux 9

Classification

Weakness
  • CWE-378 Creation of Temporary File With Insecure Permissions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.