CVE-2024-9407VulnerabilityPublished 1 Oct 2024Updated 22 Oct 2026

CVE-2024-9407: podman · Improper Input Validation

Affects podmanSource CVE Database V5

Not known to be exploited · CVSS 4.7 Medium : upgrade to 5.2.4 when convenient.

Data as of 26 Oct 2026, 08:45 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.2.4, 1.37.4

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Local
Attack Complexity: High
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade podman to 5.2.4; buildah to 1.37.4.

Affected software

Product	Affected	Fixed in
podman	Affected <5.2.4	Fixed in 5.2.4
buildah	Affected <1.37.4	Fixed in 1.37.4
GitHubpodman`pkg:github/podman`Other threats	Affected <5.2.4	Fixed in 5.2.4
GitHubbuildah`pkg:github/buildah`Other threats	Affected <1.37.4	Fixed in 1.37.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-9407, organizations should immediately review and restrict access to Docker build environments, ensuring only trusted users have high privileges required to exploit this vulnerability. Implement strict access controls and auditing on build servers and hosts running Docker. Avoid using untrusted or external Dockerfiles that could exploit the RUN --mount bind-propagation option. If you cannot patch yet, consider disabling or limiting the use of the RUN --mount instruction with bind-propagation in Dockerfiles. Employ container build isolation techniques such as dedicated build hosts or sandboxed environments to reduce risk. Monitor file system access and SELinux logs for unusual relabeling or mount activities. Additionally, educate developers and DevOps teams about the risks of improper mount options and enforce secure coding and build practices. Consider using alternative container build tools or methods that do not expose this vulnerability if immediate patching is not possible.

Description

A vulnerability exists in the bind-propagation option of the Dockerfile RUN --mount instruction. The system does not properly validate the input passed to this option, allowing users to pass arbitrary parameters to the mount instruction. This issue can be exploited to mount sensitive directories from the host into a container during the build process and, in some cases, modify the contents of those mounted files. Even if SELinux is used, this vulnerability can bypass its protection by allowing the source directory to be relabeled to give the container access to host files.

Impact

The primary impact of CVE-2024-9407 is unauthorized access to sensitive host files and potential modification of those files during the Docker image build process. This can lead to confidentiality breaches where sensitive data such as credentials, configuration files, or proprietary information is exposed to containerized environments. Modification of host files could result in integrity violations, potentially allowing attackers to alter system configurations or implant malicious code. The ability to bypass SELinux protections further increases the risk by undermining a key security control designed to isolate containers from the host. Organizations relying heavily on Docker for building container images, especially in multi-tenant or shared environments, face increased risk of insider threats or compromised build pipelines. Although exploitation requires high privileges and local access, the vulnerability could be leveraged by attackers who have already gained partial access to escalate their control or move laterally. This could impact cloud providers, enterprises with DevOps pipelines, and development environments worldwide. The lack of known exploits suggests limited immediate threat, but the potential for serious data breaches or system compromise remains significant if exploited.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 01:47 UTC

Technical details

References

Community reviews

Related threats