Red Hat Enterprise Linux/OpenShift Container Platform Podman temp file

Summaryinfo

A vulnerability was found in Red Hat Enterprise Linux and OpenShift Container Platform. It has been rated as problematic. The impacted element is an unknown function of the component Podman. The manipulation leads to temp file. This vulnerability is referenced as CVE-2025-4953. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Red Hat Enterprise Linux and OpenShift Container Platform (version unknown). It has been rated as problematic. This issue affects an unknown function of the component Podman. The manipulation with an unknown input leads to a temp file vulnerability. Using CWE to declare the problem leads to CWE-378. Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2025-4953 since 05/19/2025. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/16/2025).

The vulnerability scanner Nessus provides a plugin with the ID 265169 (Linux Distros Unpatched Vulnerability : CVE-2025-4953), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (265169), EUVD (EUVD-2025-29612) and CERT Bund (WID-SEC-2025-2075). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Red Hat Enterprise Linux
• Open Source Podman
• Red Hat OpenShift

Productinfo

Type

• Operating System

Vendor

• Red Hat

Name

• Enterprise Linux
• OpenShift Container Platform

License

• commercial

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion