CVE-2025-4953 is a high-severity (CVSS 7.4) CWE-378 vulnerability in github.com/containers/podman/v5. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Podman: build context bind mount
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-4953.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/containers/podman/v5Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/containers/podman/v5 | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/podman/v5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/containers/podman/v5 for CVE-2025-4953. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
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…
Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.Source: Red Hat security advisory for CVE-2025-4953 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | container-tools:rhel8-8100020250911075811.afee755d | RHSA-2025:15904 |
| Red Hat OpenShift Container Platform 4.12 | podman-3:4.2.0-15.rhaos4.12.el9 | RHSA-2025:17669 |
| Red Hat OpenShift Container Platform 4.12 | openshift/ose-rhel-coreos-8:412.86.202601061735-0 | RHSA-2026:0316 |
| Red Hat OpenShift Container Platform 4.13 | buildah-1:1.29.1-5.rhaos4.13.el9 | RHSA-2024:8690 |
| Red Hat OpenShift Container Platform 4.13 | buildah-1:1.29.5-1.rhaos4.13.el8 | RHSA-2025:2703 |
| Red Hat OpenShift Container Platform 4.13 | openshift/ose-rhel-coreos-9:413.92.202511261311-0 | RHSA-2025:22275 |
| Red Hat OpenShift Container Platform 4.14 | openshift/ose-rhel-coreos-9:414.92.202512031525-0 | RHSA-2025:22732 |
| Red Hat OpenShift Container Platform 4.15 | openshift/ose-rhel-coreos-9:415.92.202512100122-0 | RHSA-2025:23113 |
Frequently Asked Questions
Is CVE-2025-4953 in your dependencies?
Find it across Go, including transitive dependencies.