Metrics
Affected Vendors & Products
Solution
No solution given by the vendor.
Workaround
Avoid long-running build steps and overly permissive file permissions. Use RUN --mount=type=secret for sensitive data instead of bind mounts.
Tue, 16 Sep 2025 17:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Tue, 16 Sep 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | Podman: build context bind mount | |
First Time appeared |
Redhat
Redhat enterprise Linux Redhat openshift |
|
Weaknesses | CWE-378 | |
CPEs | cpe:/a:redhat:openshift:4 cpe:/o:redhat:enterprise_linux:10 cpe:/o:redhat:enterprise_linux:8 cpe:/o:redhat:enterprise_linux:9 |
|
Vendors & Products |
Redhat
Redhat enterprise Linux Redhat openshift |
|
References |
| |
Metrics |
cvssV3_1
|

Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2025-09-16T16:15:21.591Z
Reserved: 2025-05-19T11:55:32.522Z
Link: CVE-2025-4953

Updated: 2025-09-16T16:15:18.848Z

Status : Received
Published: 2025-09-16T15:15:45.313
Modified: 2025-09-16T15:15:45.313
Link: CVE-2025-4953

No data.

No data.