Local file exposure via retained bind-mount writes
Published Sep 16, 2025 · Updated Sep 16, 2025
Temporary-file exposure in Podman builds on Red Hat Enterprise Linux 8 and OpenShift 4 allows local users to read build-context files. During RUN --mount=type=bind, Podman preserves container-written data in a temporary host build-context directory instead of discarding it. Exposure requires concurrent unprivileged host access, a long-running build step, and permissive file modes; running containers are not compromised.
Summary
What happened
Temporary-file exposure in Podman builds on Red Hat Enterprise Linux 8 and OpenShift 4 allows local users to read build-context files. During RUN --mount=type=bind, Podman preserves container-written data in a temporary host build-context directory instead of discarding it. Exposure requires concurrent unprivileged host access, a long-running build step, and permissive file modes; running containers are not compromised.
The record
- CVE
- CVE-2025-4953
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-378, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo