Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Buildah: podman: improper input validation in bind-propagation option of dockerfile run --mount instruction

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-9407

Published

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.

Source published
1 Oct 2024 20:13:29 UTC
Source modified
5 Nov 2026 14:45:14 UTC
Saved here
5 Nov 2026 15:36:24 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2024-3036

Published

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 1, 2024, 8:13:29 PM

dateUpdated: Nov 5, 2026, 2:45:14 PM

21 related source bulletins · separate from aliases

SUSE-SU-2024:3988-1: Security update for buildah

CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676

SUSE-SU-2025:20143-1: Security update for podman

CVE-2023-45288 · CVE-2024-11218 · CVE-2024-6104 · CVE-2024-9407 · CVE-2025-27144

RHSA-2024:9459: Red Hat Security Advisory: buildah security update

CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676 · CVE-2024-34155 · CVE-2024-34156 · CVE-2024-34158

SUSE-SU-2024:3545-1: Security update for buildah

CVE-2024-9341 · CVE-2024-9407

msrc_CVE-2024-9407: Buildah: podman: improper input validation in bind-propagation option of dockerfile run --mount instruction

CVE-2024-9407

RHSA-2024:9051: Red Hat Security Advisory: podman security update

CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676

RHSA-2024:10147: Red Hat Security Advisory: OpenShift Container Platform 4.16.24 security update

CVE-2024-9341 · CVE-2024-9407 · CVE-2024-24786

RHSA-2024:9454: Red Hat Security Advisory: podman security update

CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676 · CVE-2024-34155 · CVE-2024-34156 · CVE-2024-34158

openSUSE-SU-2024:0350-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-0132 · CVE-2024-0133 · CVE-2024-10005 · CVE-2024-10006 · CVE-2024-10086 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-10452 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-39720 · CVE-2024-46872 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47401 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50052 · CVE-2024-50312 · CVE-2024-50354 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8185 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

openSUSE-SU-2024:14447-1: govulncheck-vulndb-0.0.20241030T212825-1.1 on GA media

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

SUSE-SU-2025:20080-1: Security update for podman

CVE-2024-6104 · CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676

openSUSE-SU-2024:14388-1: buildah-1.37.4-1.1 on GA media

CVE-2024-9341 · CVE-2024-9407

RHSA-2024:8846: Red Hat Security Advisory: container-tools:rhel8 security update

CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675

SUSE-SU-2025:20279-1: Security update for podman

CVE-2023-45288 · CVE-2024-11218 · CVE-2024-1753 · CVE-2024-3727 · CVE-2024-9407 · CVE-2025-22869 · CVE-2025-27144

SUSE-SU-2024:4303-1: Security update for buildah

CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676

SUSE-SU-2025:0320-1: Security update for buildah

CVE-2024-11218 · CVE-2024-9407

RHSA-2024:9926: Red Hat Security Advisory: buildah security update

CVE-2024-9407 · CVE-2024-9676

SUSE-SU-2024:3741-1: Security update for podman

CVE-2024-9407 · CVE-2024-9675

openSUSE-SU-2024:14390-1: podman-5.2.4-1.1 on GA media

CVE-2024-9341 · CVE-2024-9407

SUSE-SU-2024:3911-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

SUSE-SU-2025:0775-1: Security update for podman

CVE-2023-45288 · CVE-2024-11218 · CVE-2024-1753 · CVE-2024-6104 · CVE-2024-9341 · CVE-2024-9407 · CVE-2024-9675 · CVE-2024-9676 · CVE-2025-27144

Source published
Oct 1, 2024, 8:13:29 PM (timezone not stated)
Source modified
Nov 5, 2026, 2:45:14 PM (timezone not stated)
Saved here
15 Nov 2026 03:33:30 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

nvd · CVE-2024-9407

Published

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-20

Original publisher date fields

published: 2024-10-01T21:15:08.530

lastModified: 2026-11-05T15:17:03.580

Source published
1 Oct 2024 21:15:08 UTC
Source modified
5 Nov 2026 15:17:03 UTC
Saved here
6 Nov 2026 05:36:38 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 4.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:N

osv · GHSA-fhqq-8f65-5xfc

Published

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.

Source published
1 Oct 2024 21:31:35 UTC
Source modified
10 Sep 2026 03:50:19 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Publisher rating · MODERATE

osv · GO-2024-3169

Published

Improper Input Validation in Buildah and Podman in github.com/containers/buildah

Source published
9 Oct 2024 20:29:23 UTC
Source modified
4 Feb 2026 03:01:05 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current